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
I am not entirely sure whether this is a bug or not, as the spec seems vague to me about the behavior of /= statements preceded by a = statement, but this sentence seems to suggest that it should behave the same:
It is not an error if a name is first used with a "/=" or "//=" (there is no need to "create it" with "=").
I stumbled upon this while validating the following CDDL. Apologies for the length, I haven't gotten around to simplifying it yet.
Perhaps it won't be necessary if I am found to be misinterpreting the spec. The offending operator is on line 3.
I am not entirely sure whether this is a bug or not, as the spec seems vague to me about the behavior of
/=
statements preceded by a=
statement, but this sentence seems to suggest that it should behave the same:I stumbled upon this while validating the following CDDL. Apologies for the length, I haven't gotten around to simplifying it yet.
Perhaps it won't be necessary if I am found to be misinterpreting the spec. The offending operator is on line 3.
The text was updated successfully, but these errors were encountered: