If it’s ridiculous that I hijack this thread for related followup, please, mods, feel free to fork it.
Question: why not make std.testing.Smith.constructInput() pub? Here’s my angle: when noodling some test code for the fuzzer to run, it’s nice that a normal test run (even zig test, without zig build) runs the given fuzz function once through. However, normally the smith’s .in is not conducive to a run-through that exercises much of the code (in some basic cases I’m playing with). So, I’m forced to a bit of contrivance. If I could just sample-feed, via constructInput(), as is done in some basic concept testing in std.testing.Smith, I could get a single run that is more representative of “normal” (actually exercising more of the code), then I could be more confident when firing off the fuzzer.