| commit | 120dac365d4893adf7cb15d5d610b3418321abf9 | [log] [tgz] |
|---|---|---|
| author | Slava Egorov <vegorov@google.com> | Thu Sep 12 08:25:27 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 12 08:25:27 2024 +0000 |
| tree | 4371dc30cfdcc26d491149d828c4779c006629c2 | |
| parent | e106b7bf09f6c7c4d1585291d23d650dcb9675f4 [diff] |
Revert "[vm] Simplify implementation of native ports" This reverts commit 5a32d8bc7c5569efde3aec844b7f26d33e1bd86e. Reason for revert: DartIsolateTest.CanCreateServiceIsolate flutter engine unit test hangs on Windows. Original change's description: > [vm] Simplify implementation of native ports > > This CL turns native ports into a thin abstraction over underlying > thread pool instead of building them as full fledged MessageHandler. > > This allows to easily implement a variation of native ports which can > handle messages concurrently with the given degree of concurrency. > This type of port can be used to greatly simplify implementation of > IOService - which previously had to do its own concurrency management > on top of "single threaded" native ports. This capability is exposed > as `Dart_NewConcurrentNativePort` API. > > The new implementation is in general much cleaner then the old one > with one exception: `Dart_CloseNativePort` API has unfortunate design > where underlying message handler is destroyed asynchronously and > `Dart_CloseNativePort` returns immediately without waiting for pending > tasks to complete. Implementing this on top of `ThreadPool` requires > some changes to thread pool implementation. > > Issue https://github.com/dart-lang/sdk/issues/55844 > > TEST=ci > > Change-Id: I062040ff233e93962ae93684e9b044d8facdaffc > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/382163 > Commit-Queue: Slava Egorov <vegorov@google.com> > Reviewed-by: Martin Kustermann <kustermann@google.com> Change-Id: I7de27793a54072e974bf1a9f17a07c12159a202d No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/384481 Commit-Queue: Slava Egorov <vegorov@google.com> Reviewed-by: Martin Kustermann <kustermann@google.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
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).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
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).
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 in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.