Changes for language spec update? compiler-inserted default_action is not const #452
Labels
p4-language-compatibility
An issue related to compatibility between P4_16 language spec and P4Runtime API spec
This issue is related to the following change made from v1.2.3 to v1.2.4 of the P4_16 language specification:
Basically, if a table definition has no explicit
default_action
property, the compiler behaves as if the user wrote the propertydefault_action = NoAction();
, and addsNoAction
to the list of actions if it was not there already.(see https://p4.org/p4-spec/docs/P4-16-v1.2.4.html#sec-summary-of-changes-made-in-version-124 for the item in context of the full list of changes, but there are separate Github issues for each that might impact the P4Runtime API specification).
This seems worth at least briefly discussing in API work group, but my guess is that this is really just a clarification in the language spec that says explicitly what has already been done for years in the open source P4 implementations.
The text was updated successfully, but these errors were encountered: