You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why should this rule be added? Share links to existing discussion about what
the community thinks about this.
weak on a computed property doesn't do anything.
There arediscussions about adding a warning on the compiler directly.
Provide several examples of what would and wouldn't trigger violations.
classA{varb1:B{returnB()}// ok
weak varb2:B?// ok
weak varb3:B?{returnnil}// warning
weak varb4:B?{// warningget{return b3 }set{ b3 = newValue }}}
Should the rule be configurable, if so what parameters should be configurable?
Just severity
Should the rule be opt-in or enabled by default? Why?
See README.md for guidelines on when to mark a rule as opt-in.
I think it should be enabled by default. The only reasonable case for allowing this is to document the behavior, but since it's really not enforced by the compiler I'm not sure if it's worth the possible confusion.
The text was updated successfully, but these errors were encountered:
New Issue Checklist
New rule request
the community thinks about this.
weak
on a computed property doesn't do anything.There are discussions about adding a warning on the compiler directly.
Just severity
See README.md for guidelines on when to mark a rule as opt-in.
I think it should be enabled by default. The only reasonable case for allowing this is to document the behavior, but since it's really not enforced by the compiler I'm not sure if it's worth the possible confusion.
The text was updated successfully, but these errors were encountered: