Andy Fingerhut

Thanks for the pointer, Mihai, but I do not see that this proposal is aided by having a constructor for a packet_in instance. If approach (1) in my comment above...

I spoke with Nate Foster about this issue briefly, and I plan to talk one-on-one with Alan Lo about the proposal that led to this question, to see what next...

With the recent changes to the grammar.mdk file in the p4-spec repo, running these scripts mechanically gets to versions of grammar.mdk and p4parser.ypp from the p4lang/p4c repo that are under...

As of commit 4 on this PR, I am done modifying it now. If you run it with latest p4c and p4-spec repos, there are only 27 "hunks" of difference...

Comment on p4c changes currently being considered to implement `...` behavior, that might be relevant when considering what to do about this language spec issue: https://github.com/p4lang/p4c/pull/2368#issuecomment-1063092163 (and my comment replying...

Currently `, ...` at the end of a list expression means that all other fields of the struct or header that have not yet had a value specified for them...

@jnfoster Sounds good to me. Happy to do some nudging, if it helps. I know that `...` is "only syntactic sugar", i.e. any program written using `...` can be written...

There are no spec changes here, only updates to some slightly outdated list of supported Ubuntu Linux versions on which the bash install script is known to work.

I am certainly open to other syntactic ideas, certainly. I know there is a preference/guidance against using annotations for things that significantly change the meaning of the program if they...

@apinski-cavium I agree that if we want to preserve backwards compatibility with very very commonly written P4 code, we should not make a change where we _mandate_ that directionless parameters...