| commit | 6e249578f6ab7786c672481bc71f390a4ff4e360 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Thu Sep 26 13:38:13 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 26 13:38:13 2024 +0000 |
| tree | 973417ad8ad270c6107c00b0e7cb1165264a602a | |
| parent | 72c2e73f0b195d2daf4739ac8be0ba27e3633ff0 [diff] |
Add unit tests for _fe_analyzer_shared subtype functionality. These tests cover just the portion of the subtype constraint generation mechanism that's currently shared between the analyzer and the CFE. I plan to add more unit tests as more functionality becomes shared. Note that as part of this change, I've eliminated the methods `performSubtypeConstraintGenerationForFutureOrRightSchema` and `performSubtypeConstraintGenerationForFutureOrLeftSchema`, and instead made `_performSubtypeConstraintGenerationForFutureOrInternal` public (renaming it to `performSubtypeConstraintGenerationForFutureOr`). My rationale for this change is as follows: - It makes testing easier, since only one method needs to be tested rather than two. - Removing these two methods simplifies the call sites in the analyzer and CFE, since instead of having to use an `if` test to decide which method to call, they can simply pass in the appropriate boolean switch for the `leftSchema` argument. Change-Id: I0911c80fc8e9a4fbdd3dd0063dd203066006c218 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/386861 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Chloe Stefantsova <cstefantsova@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.