-
Notifications
You must be signed in to change notification settings - Fork 72
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
Add a FuzzyEq trait #50
Comments
I agree about The downside of the comprehensiveness of the |
Yea, that sounds about right. I'd be curious to see what the API actually looks like, if you have a branch? |
We talked at the xilem office hours. We decided that the best way forward is to experiment with using |
Why not expose it with an option like IOF does? |
Doing it in tests doesn't preclude adding it in future.
…On Wed, 22 Mar 2023, 18:40 Fredrick Brennan, ***@***.***> wrote:
Why not expose it with an option like IOF does?
—
Reply to this email directly, view it on GitHub
<#50 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKT4XSEWDSEUSTCJBURTFLW5NBS3ANCNFSM4IG5KHTQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
We should have a floating-point aware equality comparison. There are crates out there that provide this logic, and I think it's tricky enough that it's worth a dependency if somebody has done it well.
I suspect the best way to do this would be via some sort of
FuzzyEq
trait. the float-cmp crate looks like a likely candidate, but I would ideally like something that could, say, infer a good epsilon value for you based on the input values, although maybe this is a bit optimistic.The text was updated successfully, but these errors were encountered: