[3.2] Mention NativeCallable in the ObjC multithreading limitations
#5336
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
Thanks for updating this and the heads up! I likely won't merge this until after the 3.2 stable API docs are available, so it should be fine :) |
parlough
changed the title
NativeCallable in the ObjC multithreading limitations
20 tasks
Closed
atsansone
pushed a commit
to atsansone/site-www
that referenced
this pull request
Jan 26, 2024
…dart-lang#5336) Mention the new `NativeCallable` API in the ObjC multithreading limitations section. It's no longer true that *all* Dart callbacks will cause the app to crash when invoked from the wrong thread. Fixes dart-lang#5333 --------- Co-authored-by: Parker Lougheed <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mention the new
NativeCallableAPI in the ObjC multithreading limitations section. It's no longer true that all Dart callbacks will cause the app to crash when invoked from the wrong thread.Fixes #5333