docs should clearly detail that objective-c callbacks are scoped to an isolate

Open Beginner friendly
#3,264 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
dart, objective-c
Domain
documentation

Research direction

Open the Objective-C interop documentation at the callbacks-and-multithreading-limitations section linked in the issue. Read the surrounding callback and isolate guidance, then add a clear warning that the VM crashes when a callback runs after the isolate that registered it exits. Done means the isolate-scoping and crash behavior are explicit and easy to find.

Written by the indexing model from the issue text.

Description

lang-objective_c package:ffi type-documentation

The documentation should explain that the VM will crash if an Objective-C callback occurs after the exit of the isolate that registered the callback.

Maybe this would the appropriate place to add the documentation:
https://dart.dev/interop/objective-c-interop#callbacks-and-multithreading-limitations

Dominant language
Dart
Stars
274
Forks
147
Avg merge
2d 1h
Merged PRs (30d)
57

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dart-lang/native

All issues in dart-lang/native

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.