Nate Foster
The parser has some special logic to allow keywords like `type` to be used as identifiers when there is no ambiguity. For example: https://github.com/p4lang/p4c/blob/main/frontends/parsers/p4/p4parser.ypp#L447 I'm not surprised there are some...
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...
This semantics seems more natural, so let's leave this open for now...
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...
I agree. Let's see if we tighten up the spec, but perhaps not go as far as mandating N phases, for large N...
I believe there may be a separate issue. Perhaps @mbudiu-vmw can weigh in: are functions not being type checked as they are declared, but only after being inlined?
I think this is subsumed by #1213.
The [specification](https://p4.org/p4-spec/docs/P4-16-v1.2.0.html#sec-table-action-list) says, > The expressions supplied as arguments to an action are not evaluated until the action is invoked which seems consistent with what's written above (if a bit...
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...
I'd merged this prematurely at the last LDWG...