-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
fix treat_as_floating_point_v<_DurationType>
#2638
Conversation
Co-authored-by: Daniel Krügler <[email protected]>
Thanks! (I especially appreciate the added test coverage.) To avoid the need to suppress compiler warnings, I went ahead and pushed what looks like a major rearrangement, but is actually a few simple transformations:
I believe that the resulting code reads naturally: "At compile-time, if we're not treating the rep as floating-point, then we're treating it as integral (which might lose precision). We'll need For the treat-as-floating-point case, there is an extremely minor throughput advantage to Hope this is okay - it's a bit larger than the changes I usually push without asking. |
Good.
So this is why I did "pragma push"... |
Ah, thanks - I had forgotten we still had some of those. I'll go through and clean up (in a separate PR) as many of the 4127 suppressions as possible/convenient (most of them date back to when we couldn't use |
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
Thanks again for fixing this bug and testing the affected parsing scenario! 😻 🐞 🎉 |
Fixes #2636