-
Notifications
You must be signed in to change notification settings - Fork 9
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
round trip issue #4
Comments
Indeed those two do not pass. I fixed running nunit tests with vs2022 here https://github.com/rotanov/grisu.net/tree/fix_nunit Also last time I noted this it seemed that it's was only possible to reproduce on:
But it didn't fail on Ryzen 7 2700X. And now it fails again on i7-11800H. Also at one point I thought maybe if something wrong with Judging by pull requests may be @shunter can help somehow? |
It's probably worth checking the implementation against the original C++ implementation, especially if there were changes since it was ported. I'm afraid I haven't used this project for several years now, so I don't have any particular insight into what might be wrong. |
Alright, this seems to be the valid mirror for the original C++ implementation (https://github.com/stlab/double-conversion). I'll return with a pull request if I manage to locate the issue when I have time for that. Thanks! |
Maybe the behavior in Double.Parse is related to this issue: dotnet/runtime#4406. edit: I 95% sure it's the source of the issue. Resolution is to use IEEE compliant double parser instead of C#'s |
during tests on random values I've found several cases where the generated string won't do the round trip to the original value e.g.:
431.45061948654927 -> 431.45061948654933
27.201309524416448 ->27.201309524416452
...
The text was updated successfully, but these errors were encountered: