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
Following on from this comment, the Sysl parser currently parses parenthetical primitive constraints that have never been officially supported. Consider the following examples of types that parse correctly but have never been officially supported:
All other representations should be considered invalid.
Suggested approaches
The corpus of Sysl files should first be searched to see if any of the unsupported representations are being used. The parser should then either fail or warn when an unsupported representation is discovered (depending on how widely the representation can be found in use).
The text was updated successfully, but these errors were encountered:
Also, should we consider supporting the bitWidth constraint (from this issue) as the general approach to numeric types? For example, the representation of the following types would be (taking into considering their currently parsed values):
Purpose
Following on from this comment, the Sysl parser currently parses parenthetical primitive constraints that have never been officially supported. Consider the following examples of types that parse correctly but have never been officially supported:
The following is the list of officially supported parenthetical primitive type constraints and their expected representation:
All other representations should be considered invalid.
Suggested approaches
The corpus of Sysl files should first be searched to see if any of the unsupported representations are being used. The parser should then either fail or warn when an unsupported representation is discovered (depending on how widely the representation can be found in use).
The text was updated successfully, but these errors were encountered: