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
scheglov opened this issue
Oct 31, 2013
· 4 comments
Labels
area-testCross-cutting test issues (use area- labels for specific failures; not used for package:test).type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
It is a compile time error if the expression is not one of the following:
- A reference to a compile-time constant variable.
- The name of a class.
- A call to a constant constructor.
There was a long discussion about this metadata issue between Peter, Gilad, and Ivan. I am not sure if there was a definitive resolution, though.
Reassigning to Ivan.
area-testCross-cutting test issues (use area- labels for specific failures; not used for package:test).type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
From specification:
It is a compile time error if the expression is not one of the following:
- A reference to a compile-time constant variable.
- The name of a class.
- A call to a constant constructor.
I don't understand why it was changed in https://codereview.chromium.org/24789003/
Analyzer (will) reports compile-time error and tests runner does not understand specifying both (or I don't know how to do this).
The text was updated successfully, but these errors were encountered: