[#1362] Clarify that switch statements _are_ allowed in action/function bodies, and that switch statements with action_run expressions are only allowed in control apply blocks
#1363
Conversation
Signed-off-by: kfcripps <[email protected]>
|
So this does work in the P4C, right? |
@vlstill For backends that don't run the |
| This type of `switch` statement can only be used within control `apply` | ||
| blocks. For this variant of `switch` statement, the expression must be | ||
| of the form `t.apply().action_run`, where `t` is the name of a table | ||
| (see <<sec-invoke-mau>>). All switch labels must be names of |
There was a problem hiding this comment.
Isn't this implicit from the fact that table.apply() can only be used in control apply blocks, not in functions or actions?
There was a problem hiding this comment.
"This type of switch statement can only be used within control apply blocks." is definitely implied by other parts of the spec, but it seems reasonable to say here, too.
There was a problem hiding this comment.
I also don't think it hurts to explicitly state that here, but if anyone strongly opposes it I can remove it.
The other clarifications are the most important parts of this PR.
Cleans up some wording that was missed by #945, which makes it unclear as to whether
switchstatements are actually supported in actions/functions or not.Closes #1362.