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

Conversation

@stephentoub
Copy link
Member

@stephentoub stephentoub commented Apr 13, 2018

Copy-and-paste error while adding in the Span-based overload led to these having the wrong default style. This wasn't caught by tests because a) the existing string-based tests were using the wrong default style (probably also a copy-and-paste error) such that the relevant string-based overloads weren't actually being tested as thought, and b) that code wasn't added to the span-based tests anyway. I've fixed the ref, fixed the string-based tests, and copied/modified the tests for the span-based overloads as well.

Fixes https://github.com/dotnet/coreclr/issues/17553
Related to dotnet/coreclr#17556
cc: @jkotas

Copy-and-paste error while adding in the Span-based overload lead to these having the wrong default style.  This wasn't caught by tests because a) the existing string-based tests were using the wrong default style (probably also a copy-and-paste error) such that the relevant string-based overloads weren't actually being tested as thought, and b) that code wasn't added to the span-based tests anyway.  I've fixed the ref, fixed the string-based tests, and copied/modified the tests for the span-based overloads as well.
@stephentoub stephentoub added this to the 2.1.0 milestone Apr 13, 2018
@stephentoub
Copy link
Member Author

@dotnet-bot test OSX x64 Debug Build please (HttpListener test)

@stephentoub stephentoub merged commit 1e0148b into dotnet:master Apr 14, 2018
@stephentoub stephentoub deleted the fixdefaultarg branch April 14, 2018 00:47
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
…efx#29099)

Copy-and-paste error while adding in the Span-based overload lead to these having the wrong default style.  This wasn't caught by tests because a) the existing string-based tests were using the wrong default style (probably also a copy-and-paste error) such that the relevant string-based overloads weren't actually being tested as thought, and b) that code wasn't added to the span-based tests anyway.  I've fixed the ref, fixed the string-based tests, and copied/modified the tests for the span-based overloads as well.

Commit migrated from dotnet/corefx@1e0148b
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Default NumberStyle in float.Parse and double.Parse is Integer for Span

3 participants