stc.experimental.ndslice -> sci.ndslice

[ag0aep6g via Digitalmars-d]

On 17.04.2016 11:44, Ilya Yaroshenko wrote:
> This would be a real pain for a user if he supports few compiler versions.
>
>
> static if(__VERSION__ < 2072)
> {
>      import std.experimental.sci.ndslice;
> }
> else
> {
>      import std.sci.ndslice;
> }
[...]

Breakage is what you sign up for when using experimental modules.

However, when std.experimental.foo moves over to std.foo, it's probably 
possible to keep the experimental name as an alias for the new one. That 
way you just import std.experimental.foo until a reasonable amount of 
past versions have std.foo. That's how it went with std.typetuple -> 
std.meta.

ndslice should move out of experimental when it's ready, not sooner. If 
this hinders the creation of other std modules, then push for ndslice to 
get ready.