Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Changing Math.Max, Math.Min, Math.MaxMagnitude, and Math.MinMagnitudeto propagate NaN inputs#24039

Merged
jkotas merged 1 commit intodotnet:masterfrom
tannergooding:propagate-nan
Apr 17, 2019
Merged

Changing Math.Max, Math.Min, Math.MaxMagnitude, and Math.MinMagnitudeto propagate NaN inputs#24039
jkotas merged 1 commit intodotnet:masterfrom
tannergooding:propagate-nan

Conversation

@tannergooding
Copy link
Copy Markdown
Member

This resolves the CoreCLR side of https://github.com/dotnet/corefx/issues/36931

@tannergooding
Copy link
Copy Markdown
Member Author

The CoreFX side is here: dotnet/corefx#36935

@tannergooding
Copy link
Copy Markdown
Member Author

CC. @karelz as an FYI

@AaronRobinsonMSFT
Copy link
Copy Markdown
Member

Do we have tests to ensure this behavior? This is one of those behaviors that people come to rely on and shouldn't be regressed less someone's models become invalid.

@jkotas
Copy link
Copy Markdown
Member

jkotas commented Apr 17, 2019

Do we have tests to ensure this behavior

Yes: dotnet/corefx#36935

@jkotas jkotas merged commit c5b2e71 into dotnet:master Apr 17, 2019
@jkotas
Copy link
Copy Markdown
Member

jkotas commented Apr 17, 2019

@Anipik Could you please check the mirror?

@Anipik
Copy link
Copy Markdown

Anipik commented Apr 17, 2019

Yes, there were some merge conflicts with mono. I resolved them and its up again. Sry for the delay

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants