Make 0.20.x version compatible with funty 1.2 #141
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
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.
Hi!
Recently I tried to introduce a new dependency into a project I'm working on and encountered this issue: #105
Unfortunately I didn't find a way to solve this dependency compilation failure in my project, as we already have another dependency that requires bitvec 0.22.x which requires funty 1.2. The new dependency I want to introduce requires bitvec 0.20.x which isn't compatible with funty 1.2; and it seems it's not possible to have funty 1.1 and funty 1.2 at the same time.
This PR is an update from #110 but for the latest release in the 0.20.x version. It makes bitvec 0.20.x work with funty 1.1 and funty 1.2. I've also updated the version in
Cargo.tomlto 0.20.5 and would like to ask if you could publish this release to crates.io.I didn't find any branch for the 0.20.x version, so I made the PR agains develop, but it obviously is not compatible. Is there a better way for me to submit a PR for the 0.20.x branch?