commit | 37fba7b9dcfa6a0d545ec7591d9166c80346eff8 | [log] [tgz] |
---|---|---|
author | Nate Biggs <natebiggs@google.com> | Thu Aug 03 22:13:40 2023 +0000 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 03 22:13:40 2023 +0000 |
tree | 463fe7127c7ce1ba0905084c005e4e8f4297afd1 | |
parent | 29dcf293146044abdc4b77000c616bd69b32c8fc [diff] |
[dart2js] Add alias mapping for deferred import IDs. Today the deferred import mapping is missing a way to match a specific user-defined deferred load alias to a corresponding runtime load ID. This adds a new field, "importPrefixToLoadId", under each library entry, which is keyed by library URI, which maps from the user-defined deferred load ID to the Dart2JS runtime load ID. Example using https://github.com/dart-lang/sdk/blob/main/tests/language/deferred/split_constants_canonicalization_test.dart: ``` { "_comment": "This mapping shows which compiled `.js` files are needed for a given deferred library import.", "split_constants_canonicalization_test.dart": { "name": "<unnamed>", "imports": { "1": [ "out.js_1.part.js" ], "4": [ "out.js_2.part.js" ] }, "importPrefixToLoadId": { "a": "1", "b": "4" } }, "split_constants_canonicalization_a.dart": { "name": "<unnamed>", "imports": { "2": [ "out.js_4.part.js", "out.js_3.part.js" ], "3": [ "out.js_4.part.js", "out.js_5.part.js" ] }, "importPrefixToLoadId": { "a_1": "2", "a_2": "3" } }, "split_constants_canonicalization_b.dart": { "name": "<unnamed>", "imports": { "5": [ "out.js_4.part.js", "out.js_6.part.js" ], "6": [ "out.js_4.part.js", "out.js_7.part.js" ] }, "importPrefixToLoadId": { "b_1": "5", "b_2": "6" } } } ``` Change-Id: Ia6a6f8e45613c0081485e3fe5ddc84627749ee8e Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/317222 Reviewed-by: Sigmund Cherem <sigmund@google.com> Commit-Queue: Nate Biggs <natebiggs@google.com>
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).
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.