Right now, running tests consist of running anodizer to generate structs and then running the tests with vw. It would be a much better user experience/maintenance improvement to have vw automatically generate this struct file as part of the test build flow by pulling anodizer in as a library.
This can vary in complexity from just running anodizer every time you run a test to doing tracking of modified files and only regenerating if files are modified since the last run.
For long, long term, we may also want to consider generating structs via proc-macro like we do in p4 (https://github.com/oxidecomputer/anodizer/issues/1)
Right now, running tests consist of running
anodizerto generate structs and then running the tests withvw. It would be a much better user experience/maintenance improvement to havevwautomatically generate this struct file as part of the test build flow by pullinganodizerin as a library.This can vary in complexity from just running
anodizerevery time you run a test to doing tracking of modified files and only regenerating if files are modified since the last run.For long, long term, we may also want to consider generating structs via proc-macro like we do in p4 (https://github.com/oxidecomputer/anodizer/issues/1)