| commit | c1366a48e9df1d7b9fdc5d197445e2f914fca4dc | [log] [tgz] |
|---|---|---|
| author | Konstantin Shcheglov <scheglov@google.com> | Tue May 06 13:34:28 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 06 13:34:28 2025 -0700 |
| tree | c16ff3d7984adc7ea08d5ab6de65dee6101a9afe | |
| parent | 50e0e0d99df1f1a581882c86eaaf785766945d29 [diff] |
Fine. Add a few tests that ask element model manually. These tests just record requirements, but don't verify that these requirements cause re-computation of the result if changed. My current thinking is that we might have two main axis of tests: library manifests that verify that we give new IDs to changed elements; and requirements that verify that asking a piece of data from the element model is recorded as a requirement (or not, if this piece of data already cause the element ID to change). We need at least one test for each requirement kind that verifies that such requirement does cause re-computation. But we don't need to do this in every test. So, we avoid combinatorial explosion of cases? E.g. if there are two requirements recorded, we don't want to try all 4 combinations how they change. Change-Id: Iab9b0f1cd7749bc4f3c404efa340b4722bb0214e Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/426661 Reviewed-by: Paul Berry <paulberry@google.com> Commit-Queue: Konstantin Shcheglov <scheglov@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 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.