adding static return?
Stanislav Blinov
stanislav.blinov at gmail.com
Mon Mar 3 15:41:31 PST 2014
I don't get it. That should be a static assert, not static if.
Why would you even add into your build order a module that will
never be actually compiled?
If anything, static assert will prevent dead imports while such
"static return" will silently swallow them.
How would you propose handling module constructors and
module-scope variables in presence of such return?
More information about the Digitalmars-d-learn
mailing list