emil-e
emil-e
Nice! I will review this as soon as I have the time, have been a little busy lately :)
Will continue review later.
UTF8 is obviously the most important since that is likely what goes into `std::string`. Specifying ranges would also be nice but for `arbitrary` the range should be based on size....
If you generate code points that you map to the respective encoding, you can just shrink those and the bytes in the UTF8 characters will become fewer automatically. UTF32 will...
Really happy when people contribute! Some thoughts: - In your case, the problem was the absolute number of commands that were generated. If the way the sequence length is determined...
It's not always easy to come with the right solution, you hsve to strike the right balance between usability and flexibility. One thing I've been thinking about is to have...
The length of the command sequence that `rc::state::check` uses is based on the size (currently a random number between `0` and `size`) so simply scaling the size would give you...
The disadvantage of using `scale` to undo the downscaling is that you lose precision since the size is integral. But that probably does not matter a lot in this case....
The hacky way to cache the size would be to have a generator that simply generates the current size but I won't show you how to because it's not something...
Another idea, if the are other commands that can still be applied once you've reached the limits of numeric precision, you can include the number of precision breaking command in...