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

SemVer backwards incompatible change in 0.2.6 #11

Open
bsteinb opened this issue Feb 23, 2019 · 1 comment
Open

SemVer backwards incompatible change in 0.2.6 #11

bsteinb opened this issue Feb 23, 2019 · 1 comment

Comments

@bsteinb
Copy link

bsteinb commented Feb 23, 2019

Hi there! Version 0.2.6 contains a SemVer backwards incompatible change and should have been made 0.3. The problem is the addition of a public item (method abs()) to a trait (Ieee754). In my crate accurate I do not implement the Ieee754 trait as such, but I have it in scope together with the Float trait from num-traits which also has a method abs(). x.abs() where x: T and T: Float + Ieee754 used to be unambiguous, but with ieee754 0.2.6 it is not. I can work around this by using Float::abs(x). Just wanted to let you know.

@huonw
Copy link
Owner

huonw commented Aug 4, 2019

Ah, this is unfortunate, and it took me so long to notice this issue that I suspect it no longer matters. I'm happy to release a 0.3.0 and yank 0.2.6 if that would still help.

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

No branches or pull requests

2 participants