Wilson Snyder

I agree with the different steps/python version requirements you suggest. If we want to "autobootstrap" then I think uv is nicer, but suggest we avoid that now as will undoubtedly...

Hmm, lets rename python-dev-requirements.txt, and add insude comments it us fir dec use, runtime diesn't need it, snd usual use us via 'make venv' see internals.txt. With that feel free...

This should probably have a warning message as is probably as likely to be a mistake as intended. Pull welcome to fix this. See also #5877

This would go into V3Undriven. There are several other improvements people have suggested there too.

To solve this ideally I believe the right way is for each variable to make a used and consumed data structure. That data structure that looks a bit like a...

No, there's no way to add lint without sources. At least one "dead" commercial tool supported this using a VPI like language, I don't know for sure if others do....

Yes, the lint checks must be done at the appropriate place before possible optimizations "break" them.

I'm not sure if you are asking a Verilator specific question or a general one. For general see e.g. https://en.wikipedia.org/wiki/Abstract_syntax_tree for specifics see https://github.com/verilator/verilator/blob/master/docs/internals.rst

Once upon a time due to clocking --public would break a lot. If we're down to only these tests (ignoring those that --public causes something to print differently), we're doing...

When the interface is elaborated it seems to get a confused data type. Needs some more debug - perhaps you'd like to take a look at a pull to fix...