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
Right now any parameter of a type are transformed to a field in the generated type like a regular seq/instance attribute in all targets and, consequently, shares the same namespace. However, the compiler doesn't check that parameter names are not the same as seq/instance attributes:
Because there is no dedicated syntax in the expression language to distinguish between parameter names and other attributes, it seems that such ability most likely a bug not a feature, and should be prohibited.
The text was updated successfully, but these errors were encountered:
seq_parse_inst_id_clash.ksy: /instances/foo: error: duplicate attribute ID 'foo', previously defined at /seq/0
seq_value_inst_id_clash.ksy: /instances/bar: error: duplicate attribute ID 'bar', previously defined at /seq/1
but looks like we've missed yet another corner case. Thanks for reporting!
Right now any parameter of a type are transformed to a field in the generated type like a regular seq/instance attribute in all targets and, consequently, shares the same namespace. However, the compiler doesn't check that parameter names are not the same as seq/instance attributes:
Because there is no dedicated syntax in the expression language to distinguish between parameter names and other attributes, it seems that such ability most likely a bug not a feature, and should be prohibited.
The text was updated successfully, but these errors were encountered: