Fabian Ruffy

> The language does not define or enforce any naming conventions for P4, other than reserving names containing `__` for compiler/architecture internals. If someone wants a convention for P4 programs,...

>Maybe we could add hs.popFront() to the language too (and keep pop_front for compatibility), but this is deep within the language design area, not the compiler area. I think this...

Are the changes here merged into #4562? Can this be closed?

> Hi @fruffy! What is the motivation to turn libGC into a submodule? Do we need something from a specific new version? Even if so, is submodule really a good...

> I see. I've noticed the Z3 problem with libGC but did not investigate it further. It is good that it can be fixed on libGC side. > > The...

> > > libGC interacts badly with the current version of the Z3 solver (for example, #3927). A more recent version of Z3 (4.12.0) does not work at all. >...

The MacOS build fails with a bizarre error. Quite difficult to debug. Edit: It looks like the problem was that libbmv2 was not linked statically. I do not quite understand...

> > I see. I've noticed the Z3 problem with libGC but did not investigate it further. It is good that it can be fixed on libGC side. > >...

> Looks like this is still getting hung up on the fedora and old Ubuntu issues, but hopefully doesn't interoduce any more hard-to-debug dependencies. https://github.com/p4lang/p4c/pull/4623 introduced the Ubuntu 18.04 failure....

@asl Planning to merge this soon. Lmk if you have any concerns here.