Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Issue number reserved for design draft - will be welcoming feedback soon
For right now, please direct feedback to the existing Reddit thread: https://www.reddit.com/r/golang/comments/hvpr96/design_draft_first_class_fuzzing
That should include corresponding XxxUnmarshaler interfaces or you won't be able to load them back from files; the Implementation section gets that right, which might be a sign of unnecessary duplication. Suggestion: define the concept fuzzable type once, don't repeat.
By the time this proposal makes it to actual docs, definition of fuzzable types should explicitly state that the combination of built-in types with marshalable fields/values/etc are fuzzable too. Right now that is merely implied.