Jonathan DiLorenzo

We can, but I'm prioritizing PR #472 before next meeting, so I'm not convinced there will be much to say. I believe the last update here was for me to...

I think let's not make that assumption at least. If 1.4.0 ends up getting delayed sufficiently, then I may be able to, but I don't really have the cycles in...

Thanks for the ping Chris! Let's plan not to get this in for 1.4.0. I think it needs a bit more thought.

Yeah, PkgInfo feels a bit weird. But I don't think we quite want to query the platform for it... Rather, we want to tell the platform our desired capabilities and...

Based on discussions in the P4 API WG with @chrispsommers, @smolkaj, and @jafingerhut, there seems to be tentative support for adding something like this (with a few changes I'm about...

@chrispsommers, to be clear, the "changes in p4c" you're referring to is the annotation interpretation?

Added support for this PR in https://github.com/p4lang/p4c/pull/4611 (though this would need to go in first, so that the P4Info fields exist to be set).

AI: Change `multicast_table` to `multicast_group_table` and then send out again for review and we'll try to get this in before next meeting.

I think this is now ready for a final review as discussed @chrispsommers, @smolkaj, and @jafingerhut.

It looks like this didn't come up yet in the corresponding spec change, but, based on discussions in the LDWG, I think we'd prefer to keep the warnings on signed...