-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
feat: object deinit on the main thread #3633
Conversation
3c0f24e
to
6f67a14
Compare
e7dc251
to
021d99c
Compare
ce6c8cb
to
041da53
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please, take a look at the comments.
``` | ||
|
||
* If Swift/Objective-C objects are passed to Kotlin on a thread other than main or if the main dispatch queue isn't processed, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe this bullet should be a list?
Something like:
Kotlin calls deinit on the S/O objects on a specific GC thread, if:
- S/O objects are passed to Kotlin on a thread other than the main
- Main dispatch queue isn't processed (by the GC?)
If you want to call deinit on .... explicitly, set
in your gradle.properties
. This property enables deinit calls, even if these objects are passed to Kotlin on the main thread.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
No description provided.