Andy Fingerhut

All of the links reported in my original issue are working reasonably now in the version generated and published here https://p4lang.github.io/p4c/index.html after this PR was merged in: https://github.com/p4lang/p4c/pull/4793 Thus, closing...

As of commit 6 of #4753, I have confirmed that the first 2 broken links are fixed, but the last 2 are still broken.

All of the links reported in my original issue are working reasonably now in the version generated and published here https://p4lang.github.io/p4c/index.html after this PR was merged in: https://github.com/p4lang/p4c/pull/4793 Thus, closing...

Related issue: https://github.com/p4lang/p4c/issues/4813

A related comment on one technique to improve some error messages like these, and difficulties that one can encounter in using this approach, from Chris Dodd here: https://github.com/p4lang/p4c/pull/4812#issuecomment-2231758727 "In general,...

I may be missing some subtle thing that makes this program's behavior not defined according to the spec, so feel free to point out any aspect of the below that...

Here is a small test program that runs on BMv2, based on your code but with small changes to enable it to compile and run on BMv2 (e.g. make header...

If you want to guarantee in the compiler that you always detect select branches that are unmatchable, in general you will need a satisfiability solver to do it. You can...

@kfcripps Thanks for pointing those out. My main worry is if the final IR output by the compiler is functionally different from each other, not whether the IR is 100%...

I would guess that if you really wanted all of the select expressions that are equivalent to `default` to produce the same IR, and thus hopefully the same warnings and...