Skip to content
New issue

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

add some detail re: referencing .assign() and possible memory leaks #163

Open
heckj opened this issue Dec 23, 2019 · 0 comments
Open

add some detail re: referencing .assign() and possible memory leaks #163

heckj opened this issue Dec 23, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@heckj
Copy link
Owner

heckj commented Dec 23, 2019

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

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

@heckj heckj added the enhancement New feature or request label Dec 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant