While "skip measurements mode" is super useful for test coverage,
i've come to discover it's trade-offs. It still calls back-end
to actually codegen the target assembly, and that is what is taking
80%+ of the time regardless of whether or not we skip the measurements.
On the other hand, just being able to see that exegesis can come up
with a snippet to measure something, is already very useful,
and takes maybe a second for a all-opcode sweep.
I'm confused by this documentation.
Can we list the options and describe what they mean exactly?
What is the difference between skip-codegen and skip-full-codegen?
What are the outputs for the different stages?
Maybe name the options according to what they do instead of what it doesn't do.