import a.b.mixin(somwhere).here;

[IgorDeepakM]

In order open up for better modularization, it has been suggested that import should be able to use version strings to determine the import path.

One suggestion has been:
import a.b.mixin(somwhere).here;

https://forum.dlang.org/post/[email protected]

This has previously been solved by just

version(this)
{
    import xxx.this;
}
else version(that)
{
   import xxx.that;
}
...

This quickly becomes a big statement as more features/platforms are supported and files in druntime/phobos often have a big chunk of this in the beginning of each file.

The strange thing is that this has been suggested several times for several years but nothing has happened. I don't know why and nobody seems to be categorically against it either. Is the complexity high in order to implement this?

The question is if we are going to implement this in openD. Since we are going remove version with a new solution, could we also enable using them in imports as well?

Also, this change also implies that the new system would use values like in C defines rather just a check that a version identifier exists. Ex. cpu.arch = x86.

[adamdruppe]

I think a general rule of allowing mixin(thing) when an identifier is expected could be useful. Maybe that'd apply here and also do like

static foreach(name; child_members)
void mixin(name)() {}

that kind of thing.