move proptest to dev-dependencies #11
Merged
Conversation
This file contains 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
Signed-off-by: Alex Chi <iskyzh@gmail.com>
|
Haha whoops, good catch, and thanks for the PR! |
|
Huh weird CI failures, I don't think related to this? I'm going to have to dig in a bit |
|
Well, no failure for me locally, so I'm going to merge this and then dig in later |
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.
I'm recently working on porting a crate that depends on cuid to WASM and it cannot compile due to proptest uses OS-specific APIs. After looking into the source code, it turned out that proptest is a dev dependencies and we can simply move it. This enables the cuid2 crate be compatible with
wasm32-unknown-unknown.Thanks for reviews!