You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nah, what happens here is that semGenericStmt expands the dumpTree macros since it has to look at the instantiated AST, the when block is correctly evaluated at the instantiation site.
If you swap the dumpTree: ... block with a static one you'll see that when false works just fine.
sorry I fail to see the logic. Why shouldn't when false: foo just disable foo? Anything else seems buggy. Especially case1 vs case6 is inconsistent.
As it stands, when false (or when defined(posix) when we are on windows etc) is not a reliable way to disable a piece of code.
bugs:
The text was updated successfully, but these errors were encountered: