Andrew Pinski

I actually found the same issue plus the p4c is getting many new testcases for header stacks with header unions so this gets more important to fix the specifications if...

There is a testcase in the p4c already for header stacks of header unions. ./p4_16_samples_outputs/spec-ex09.p4 and p4_16_samples/spec-ex19.p4 which were added with https://github.com/p4lang/p4c/commit/bb47b71882 (well it was moved to the p4_16 directory...

So it was added in [aa88d998c3 ](https://github.com/p4lang/p4c/commit/aa88d998c31e357b8a3e217d4e39626e70ddf2f7) to support "architecture-specific conversion of P4_14 externs to P4_16". I remember looking into this while working on this area for my front-end. In...

Oh I did file this on the p4c side https://github.com/p4lang/p4c/issues/3223

As I said I was shocked coming from a C++ but I think it is decent behavior based on the rest of the P4 language. I am just trying to...

I just came across this today too. Maybe in the next spec meeting just get a vote up or down to allow them for bit. We could even add saying...

> Is the function allowed to return an object of type A? Yes, in C++14 you can return a local type by using the auto keyword and having the compiler...

Ok, I think I understand this better. So tuples used to be a synthesized type and then it was added as something the user could specify. But the feature looks...

So this comes into play when we have an expression like `{3} == {4}` is that valid or not? And is it valid as a compile time known constant too?...

https://github.com/p4lang/p4c/issues/3336 is a related issue but only because it uses bool inside a struct for the case which causes an internal compiler error :).