You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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 crateaccurate
I do not implement theIeee754
trait as such, but I have it in scope together with theFloat
trait fromnum-traits
which also has a methodabs()
.x.abs()
wherex: T
andT: Float + Ieee754
used to be unambiguous, but with ieee754 0.2.6 it is not. I can work around this by usingFloat::abs(x)
. Just wanted to let you know.The text was updated successfully, but these errors were encountered: