[dart2wasm] Avoid using `allowInterop` in Promise<->Future conversion The dart closures for the then/onError callbacks we use on a JS promise will not flow back into dart. There's therefore no reason to use the very heavyweight `allowInterop` mechanism. This makes (after [0]) asynchronous calls to JS from Dart more than 2x as fast. This also aligns the `promiseToFuture` implementation with the extension on `JSPromise` (see sdk/lib/_internal/wasm/lib/js_interop_patch.dart) modulo the fact that the API doesn't work on interop types but Dart types and needs therefore the full JS<->Dart conversion. => Maybe it would make sense to deprecate `promiseToFuture` / not offer it in dart2wasm and make users use instead the extension on `JSPromise` instead? [0] https://dart-review.googlesource.com/c/sdk/+/352520 Change-Id: Ibc80bf083e7ec817f000257d6995108954060277 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/352521 Reviewed-by: Srujan Gaddam <srujzs@google.com> Commit-Queue: Martin Kustermann <kustermann@google.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 on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.