We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seems like a point of some possible confusion, it's bit at least a few people -
using .assign() captures the reference it's handed with a strong link - not "[weak self]" kind of semantics. Detail at https://forums.swift.org/t/does-assign-to-produce-memory-leaks/29546/9
.assign()
More that the expectation of how it's handled might be made more clear - it's not really a like so much as a misunderstanding that seems common
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Seems like a point of some possible confusion, it's bit at least a few people -
using
.assign()
captures the reference it's handed with a strong link - not "[weak self]" kind of semantics. Detail at https://forums.swift.org/t/does-assign-to-produce-memory-leaks/29546/9More that the expectation of how it's handled might be made more clear - it's not really a like so much as a misunderstanding that seems common
The text was updated successfully, but these errors were encountered: