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.

unsafeOffset :: Int -> Array.Array a -> Array.Array a

and

unsafeCut :: Int -> Array.Array a -> Array.Array a

or,

unsafeSlice :: Int -> Int -> Array.Array a -> Array.Array a

@harendra-kumar Thoughts?

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!