Open
Conversation
Author
|
Any idea if this is likely to be merged soon or not? I have a PR pending for another published crate that depends on this. If its not going to be merged soon we will either need to fork this crate for crates.io or incorporate the functionality into another crate. We prefer to do neither of course. |
5 tasks
|
I have forked this crate and published It would be great if there was only one source of proptest-to-arbitrary-truth, but I want wasm-compatibility more than that. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Building for wasm32 target was failing, which is problematic for building a downstream crate with proptests that use arbitrary. Both proptest and getrandom crates support wasm32 but they require some convincing to do so. This PR convinces them.
Before
After