I agree - I took a look at the minimization algorithm[0] and it seems like it loops through a few basic options, with the last one basically normalizing all possible bytes to something readable (like "0"). Part of the issue with trying to be as generic as possible is you sometimes can't find the best solution to every problem, this might be one of those situations.
I know the goal of 1.18 was to get the UX down, so I'm interested to see how it improves for 1.19.
I know the goal of 1.18 was to get the UX down, so I'm interested to see how it improves for 1.19.
[0] https://github.com/golang/go/blob/master/src/internal/fuzz/m...