Nate Foster
It seems like this might be addressed... In any case, in the interest of tidying up the set of active issues on the P4 specification repository, I'm marking this as...
In the interest of tidying up the set of active issues on the P4 specification repository, I'm marking this as "stalled" and closing it. Of course, we can always re-open...
Closing as it seems this has been resolved in #1078.
In the interest of tidying up the set of active issues on the P4 specification repository, I'm marking this as "stalled" and closing it. Of course, we can always re-open...
And what about the fact that it can be used with `bit` too?
In the interest of tidying up the set of active issues on the P4 specification repository, I'm marking this as "stalled" and closing it. Of course, we can always re-open...
Unfortunately, `optional` is already a `match_kind` in V1Model architecture. So if we add it as a keyword (and don't do something special in the front-end) we would break one of...
Does anyone still feel strongly about this? If not, should we close it?
Given the silence, I'm going to mark this as closed.
In the interest of tidying up the set of active issues on the P4 specification repository, I'm marking this as "stalled" and closing it. Of course, we can always re-open...