Allow default nil
values for optional properties
#480
Merged
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.
This adds underscored initializers that let library users add
= nil
to declarations of optional@Option
and@Argument
properties. Previously, default values have been available for properties of non-optional types only.These new initializers use
_OptionalNilComparisonType
as the wrapped value parameter, so only anil
literal is acceptable in the default value position. This avoids the problem of declaring an optional property with a non-nil
default, which ends up negating the purpose of an optional.Checklist