[release/8.0-staging] Fix an issue with complex number parsing #104499
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #104388 to release/8.0-staging
/cc @tannergooding
Customer Impact
As per #104421, developers attempting to parse a string representing a
Complex
number would see an error for otherwise valid inputs.Regression
This was a net new API and has been broken since it was introduced.
Testing
Additional testing covering a broader range of inputs was added.
Risk
Low. This is a net new API that has overall low usage and is simply allowing valid inputs to parse as expected instead of throwing or reporting that it could not be parsed.
IMPORTANT: If this backport is for a servicing release, please verify that:
The PR target branch is
release/X.0-staging
, notrelease/X.0
.If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.