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
Hackfix for funty breaking change #250
Conversation
Not sure if we can wait until |
Yeah, I prepared this mostly to be ready if the fix is delayed. It would be better not having to merge&release it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm ok to have a 2.0.1 release with this,
I don't know how much time bitvec will take to fix it.
This is an upstream bug that should be solved by downstream projects by pinning the crate. I don't see any reason to workaround this here in our code base. |
People can just solve this by pinning the crate on their own in the |
|
bitvec 0.20.2 has been released. It fixes the issue by depending on |
Closes #249
The latest
funty
release seems to be backwards incompatible and asbitvec
importsfuncty = "1"
projects can start to break without notice. This PR doesn't address the issue but can work as a temporary solution.