| commit | 866ed841587c4ee9730203825224d2f8038eb537 | [log] [tgz] |
|---|---|---|
| author | Sigmund Cherem <sigmund@google.com> | Fri Mar 08 02:11:10 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Mar 08 02:11:10 2024 +0000 |
| tree | 5e91d07c68bb6ef8affa483c5f51d1a68aa25ce4 | |
| parent | c8d6acbfd0ea112d5a0839b3602a43d6e503568f [diff] |
[ddc] reuse the same page/script if possible on e2e tests. Since we changed how the test driver sets up breakpoints, we now we have the ability to reuse a page for multiple tests. Before, the test harness would follow this sequence: * on each group of tests, it would call `_initSource`, which sets up a boostraper and code to execute on the browser. This code was reused by all tests in the group. * on each test, it would indirectly call `_loadScript`, which navigated to brand new page for each test. If there were multiple tests in a group, this would load the boostraper and code once per test. This CL keeps the sequence of operations the same, except, that `_loadScript` will reuse the existing page if it already loaded the boostraper and DDC code needed by the next test. This greatly reduces the total running time of some of the expresison compiler shards. On my local machine one such test took 24s before both this and the parent CL, but now takes about 5s. Change-Id: I7774df9e83142b42efc4ad523f589758a2a4660c Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/356301 Reviewed-by: Nicholas Shahan <nshahan@google.com> Reviewed-by: Mark Zhou <markzipan@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.