Open Uncommon opened 5 years ago
Related to this, Swift 5.1 propertyWrappers require explicit initialisation too:
@State private var errorModal: Modal? = nil
While you're handling the Optional<Type>
case I don't suppose you could handle this too please?
Related to this, Swift 5.1 propertyWrappers require explicit initialisation too:
@State private var errorModal: Modal? = nil
While you're handling the
Optional<Type>
case I don't suppose you could handle this too please?
I believe this is just a bug in the implementation of property wrappers and is intended to be fixed.
I need it !!
I need this too, and I want to initialize everything explicitly rather than relying on some speculative default value.
Proposal: add an "inverted" configuration option to the existing
redundant_optional_initialization
rule, so that initializing variables with nil is required rather than disallowed.Also, I have found that variables declared as
Optional<Type>
rather thanType?
are not implicitly initialized to nil. The rule as currently implemented assumes that they are, so I intend to fix that while I'm at it.New Issue Checklist
New rule request
Please describe the rule idea, format this issue's title as
Rule Request: [Rule Name]
and describe:Inspired by this discussion in the Swift forums: https://forums.swift.org/t/prepitch-optional-variables-should-require-explicit-initialization-to-nil/26077
The reverse of the examples for the existing rule.
Setting
inverted: true
would treat the absence, rather than presence, of= nil
as a violation.The
inverted
configuration should default to false to preserve existing behavior.