On 4/17/16 6:04 AM, ag0aep6g wrote:
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.
Yes. In cases of moving code from std.experimental to main package (I
don't think this has happened yet), we can leave a public re-import in
std.experiemental for several releases before removing.
And we should remove it. It should not be standard to allow import
std.experimental when it has been moved to std.
-Steve
