Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

dvdplm
Copy link
Contributor

@dvdplm dvdplm commented Feb 15, 2021

Closes #249

The latest funty release seems to be backwards incompatible and as bitvec imports functy = "1" projects can start to break without notice. This PR doesn't address the issue but can work as a temporary solution.

@athei
Copy link
Member

athei commented Feb 15, 2021

Not sure if we can wait until funty gets its act together and yanks this breaking minor version.

@dvdplm
Copy link
Contributor Author

dvdplm commented Feb 15, 2021

Not sure if we can wait until funty gets its act together and yanks this breaking minor version.

Yeah, I prepared this mostly to be ready if the fix is delayed. It would be better not having to merge&release it.

Copy link
Contributor

@thiolliere thiolliere left a 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.

@bkchr
Copy link
Member

bkchr commented Feb 15, 2021

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.

@bkchr
Copy link
Member

bkchr commented Feb 15, 2021

People can just solve this by pinning the crate on their own in the Cargo.lock.

@bkchr
Copy link
Member

bkchr commented Feb 15, 2021

cargo update -p funty --precise 1.1.0

@thiolliere
Copy link
Contributor

bitvec 0.20.2 has been released. It fixes the issue by depending on funty = "~1.1". So cargo update shouldn't fail anymore.
I think we can close this then.

@thiolliere thiolliere closed this Apr 19, 2021
@thiolliere thiolliere deleted the dp-fix-funty-breaking-change branch April 19, 2021 08:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

funty 1.2 breaks constant resolution
4 participants