[stdlib] Replace .Some(x) and .None by x and nil, respectively
#470
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
|
@PatrickPijnappel Did you run the tests? Just making sure. The change LGTM. |
|
@gribozavr Ran the normal tests before, just completed the validation tests now also. All looking good. |
gribozavr
added a commit
that referenced
this pull request
Dec 13, 2015
[stdlib] Replace `.Some(x)` and `.None` by `x` and `nil`, respectively
freak4pc
pushed a commit
to freak4pc/swift
that referenced
this pull request
Sep 28, 2022
…ui-5.3 Un-XFAIL ACHNBrowserUI in debug configuration (5.3 branch)
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.
Proposal to remove explicit usage of
Optional<T>enum cases for consistency and reduced clutter (SR-212).Optional<T>takes precedence over other nil literal convertibles.Optional.swiftandImplicitlyUnwrappedOptional.swiftstill use explicit forms.