We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
According to the table in spec 7.2.8. Type nesting rules, types match_kind and int are disallowed within a tuple type.
match_kind
int
tuple
However, tests issue3091-1.p4 and issue3091.p4 accepts match_kind in tuple as valid:
match_kind { exact } const tuple<match_kind> exact_once = {exact};
And tests issue3238.p4, list3.p4, and list4.p4 accepts int in tuple as valid:
bit func(bit t1) { tuple<int> t = {t1}; return t[0]; }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
According to the table in spec 7.2.8. Type nesting rules, types
match_kind
andint
are disallowed within atuple
type.However, tests issue3091-1.p4 and issue3091.p4 accepts
match_kind
intuple
as valid:And tests issue3238.p4, list3.p4, and list4.p4 accepts
int
intuple
as valid:The text was updated successfully, but these errors were encountered: