06b2967188
The main purpose of the low-level [PortMap] is to coordinate between ports being opened & closed and concurrent message senders. That's the only thing it should do. Each isolate owns [ReceivePort]s. Only the isolate mutator can create ports, delete them or change their "keeps-isolate-alive" state. Right now it requires going via [PortMap] (which acquires lock) and [MessageHandler] (which acquires lock) to change the "keeps-isolate-alive" state of a port. We'll move information whether a dart [ReceivePort] is closed and whether it keeps the isolate alive into the [ReceivePort] object itself. => Changing the "keeps-isolate-alive" state of the port no longer requires any locks. We could even avoid the runtime call itself in a future CL. Isolates are kept alive if there's any open receive ports (that have not been marked as "does not keep isolate alive"). This is a property of an isolate not of the message handler. For native message handlers we do have a 1<->1 correspondence between port and handler (i.e. there's no "number of open ports" tracking needed). => We'll move the logic of counting open receive ports and ports that keep the isolate alive to the [Isolate]. => We'll also remove locking around incrementing/decrementing or accessing the counts. => The [IsolateMessageHandler] will ask the [Isolate] whether there's any open ports for determining whether to shut down. => For native ports, the `Dart_NewNativePort()` & `Dart_CloseNativePort()` functions will manage the lifetime (as their name also suggests). Overall this makes the [Isolate] responsible for creation of dart [ReceivePort]s and tracking whether the isolate should be kept alive: * Isolate::CreateReceivePort() * Isolate::SetReceivePortKeepAliveState() * Isolate::CloseReceivePort() TEST=ci Change-Id: I847ae357c26254d3810cc277962e05deca18a1de Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/317960 Reviewed-by: Alexander Aprelev <aam@google.com> Reviewed-by: Ryan Macnak <rmacnak@google.com> Commit-Queue: Martin Kustermann <kustermann@google.com> |
||
|---|---|---|
| .dart_tool | ||
| .github | ||
| benchmarks | ||
| build | ||
| docs | ||
| pkg | ||
| runtime | ||
| samples | ||
| sdk | ||
| tests | ||
| third_party | ||
| tools | ||
| utils | ||
| .clang-format | ||
| .gitattributes | ||
| .gitconfig | ||
| .gitignore | ||
| .gn | ||
| .mailmap | ||
| .style.yapf | ||
| .vpython | ||
| AUTHORS | ||
| BUILD.gn | ||
| CHANGELOG.md | ||
| codereview.settings | ||
| CONTRIBUTING.md | ||
| DEPS | ||
| LICENSE | ||
| OWNERS | ||
| PATENT_GRANT | ||
| PRESUBMIT.py | ||
| README.dart-sdk | ||
| README.md | ||
| sdk.code-workspace | ||
| sdk_args.gni | ||
| SECURITY.md | ||
| WATCHLISTS | ||
Dart
A client-optimized language for fast apps on any platform
Dart is:
-
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
-
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
-
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
-
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
-
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
License & patents
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Using Dart
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
Building Dart
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents on our wiki.
Contributing to Dart
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.