Update NSNumberBridging test for init(exactly:) #1273
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A fix in the behavior of FloatingPoint.init(exactly:) means that the NSNumber bridging tests need to be updated.
|
@swift-ci Please test |
|
Can the commented out code on lines 247 and 289 now be re-enabled too? |
|
@ianpartridge — good call, should've looked through the file more. GitHub doesn't want to recognize my modified commit for some reason, so I'm reopening a PR for this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A fix in the behavior of FloatingPoint.init(exactly:) means that the NSNumber bridging tests need to be updated. That fix is in swiftlang/swift#11311.