Sizeof expression #109
Sizeof expression #109
Conversation
|
Looks like that broke things during elaboration since the expression analysis hasn't happened yet at that point. It looks to me like that is a more general issue with how the elaboration works, so I'll need to investigate that further. |
AtomCrafty
force-pushed
the
sizeof-expression
branch
from
01f8b2a to
ef9f6ee
Compare
AtomCrafty
force-pushed
the
sizeof-expression
branch
from
ef9f6ee to
d432ebf
Compare
| .expectError(IssueCodes.InvalidIsaStateElementValue, 1) | ||
| .expectError(IssueCodes.UnsupportedSizeOfDuringElaboration, 3) | ||
| .expectError(IssueCodes.UnsupportedSizeOfDuringElaboration, 4) | ||
| .run(); |
There was a problem hiding this comment.
Please note this test. The way type analysis works, sizeof(255+1) (=9) is not able to be used in elaboration-time constants. This is because the types of expressions are only determined during analysis, which happens after elaboration. If we wanted to support this case we'd have to do full type analysis during elaboration, which would require a major restructuring of the analysis framework.
The constant expression evaluator has special handling of sizeof(<type>) and sizeof(<identifier>), so those can still be used, but expressions using any operator are unsupported.
2 participants
No description provided.