| commit | 355d7e02fcfbdee66a8ac2a793db24f14a7c1c42 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Tue Dec 19 02:19:39 2023 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 19 02:19:39 2023 +0000 |
| tree | 16d651b4fbbd7317e50293b403249dab785e70a6 | |
| parent | 27892de34977539de8a520ad698d098420c1a6ab [diff] |
Stop testing nnbd-weak and nnbd-legacy on analyzer. After discussion with Siggi about https://dart-review.googlesource.com/c/sdk/+/341020 (which removed a lot of mixed-mode tests from the language test suite), we've decided that these tests are worth keeping around, because they exercise important "weak mode" runtime functionality on the web platform, and weak mode is still used inside google3. However, we would like to unblock removal of legacy support from the analyzer (because this is _not_ used inside google3 anymore, and there's a nontrivial cost to maintaining it). So, to ensure that removing legacy support from the analyzer doesn't cause test failures, we need to stop running these "weak mode" tests on the analyzer platform. The test runner already has the ability to recognize these tests and skip them; it recognizes them by the comment `Requirements=nnbd-weak` at the top of the test. We simply need to instruct the test runner not to run these tests on the analyzer platform anymore. This CL also disables running of `Requirements=nnbd-legacy` tests on the analyzer. No such tests exist anymore, but since support for this requirements comment still exists in the test runner, it makes sense to include it in the effect of this CL. Change-Id: Ib5d5eb7c1bf879581b21fa5093fa7fa6304005a9 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/342080 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Sigmund Cherem <sigmund@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.