Issue 11042 - Inconsistent "static condition" behaviors

[9rnsr]

http://d.puremagic.com/issues/show_bug.cgi?id=11042

Divide SCOPEcondition and SCOPEconstraint properly.

[WalterBright]

I'm not sure this is a correct design. Consider:

static if           (is(typeof(true  || error)) == false) {} else { static assert(0); } 

The 'static if' characteristic applies to the expression inside the typeof(). But should it? I think the lazy evaluation of && and || should only apply at the top level.

[9rnsr]

The main point of issue 11042 is: The 'static if' characteristic should not affect inside typeof() and __traits(compiles).

static if (is(typeof(true || error)) == false) {} else { static assert(0); }

Even in static condition, typeof(true || error) makes error, then is(typeof(true || error)) evaluated to false.

I think the lazy evaluation of && and || should only apply at the top level.

That's what this PR is implementing.

[MartinNowak]

Sure about this? How can you get a nested scope with a template constraint?

[MartinNowak]

LGTM

[9rnsr]

Why this PR is left for one year?

[MartinNowak]

Auto-merge toggled on

[MartinNowak]

Github's makes it difficult to keep track of open pull requests, because it's notification driven.
It's always adequate to post a followup comment (e.g. ping), if something slips under the radar.

[IgorStepanov]

Github's makes it difficult to keep track of open pull requests, because it's notification driven.
It's always adequate to post a followup comment (e.g. ping), if something slips under the radar.

ping dlang/druntime#934 :)