New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change the core draw primitive to be selecting an integer from 0 to n #1986
Comments
(I pulled this out because I think it's an interesting/good idea, and I want to be able to comment on it without junking up that other thread.) |
I did some experimental work on refitting One thing I found is that some input functions naturally want to return raw bytes (e.g. sliced from an input buffer), some input functions want to return integers, and some input functions just want to generate random data in the usual way. (And some want to choose between these options depending on the circumstances.) It might be useful to allow some flexibility in allowing the input function to return bytes, or an integer, or some sentinel that instructs the caller to supply random data. Then |
Note: #1961 has lots more information that prospective implementors should read, from visualisations of the current data distribution to discussion of alternative approaches and why they won't work! |
This could also allow symbolic execution like Crosshair to exercise Hypothesis tests - an early attempt based on |
Closing this in favor of #3086 (comment); we now think that using a tree of (int, float, bytes, str) leaves will be a better underlying data structure than just integers. |
From #1961 (comment) by @DRMacIver:
The text was updated successfully, but these errors were encountered: