unicode

It just doesn't test anything for the cast majority of fuzzer input. While fuzzer does learn the effective paths, let's help it more.

First, for instruction type, change the switch argument to: instruction.operation % NUM_OPERATIONS.

Then just split the available values into the two sets by looking up one integer from fuzzer and use that module size for set1 and the rest for set2.

• Cleanup the tests
• Move module-specific tests into their own modules
• Rename the test case functions as we do in benchmarks

I've recently come to realize that the 'one-size-fits-all' mega-snippets on marzer.github.io/tomlplusplus aren't necessarily useful for everyone, and I should break them up into smaller sub-examples. I'd be totally happy to accept help with this, though that may be wishful thinking!

Purely for debugging purposes.

This option might be helpful in investigating buggy VT sequences.
This option is receiving a path to a file, defaulting to an empty string (aka. disabled).