commit | b0e488fcb25db14b5586c5093e00e427e7a54f9d | [log] [tgz] |
---|---|---|
author | Paul Berry <paulberry@google.com> | Tue Jun 03 17:10:44 2025 -0700 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 03 17:10:44 2025 -0700 |
tree | b81a5f60040e4dc20b94b97d2f34df5c76ef4831 | |
parent | cfccc2a2a845c71594f335c2f3da0cf5c0a20fa1 [diff] |
[flow analysis] In tests, stop rewriting ordinary variable declarations. During the implementation of flow analysis for patterns, I added a hack to the flow analysis tests so that all variable declarations were desugared into the equivalent pattern variable declaration. This had the advantage of getting some extra testing "for free" during early development of the patterns feature, but it had a few disadvantages: - It the caused the shared flow analysis and type inference tests to stop exercising flow analysis code paths for ordinary variable declarations. - It forced the testing logic to "support" pattern variable declarations that are late or lack an initializer; these are things that regular Dart doesn't support, and they made the implementation of `PatternVariableDeclaration.visit` much more complicated than it needed to be. The language team is currently contemplating some changes to how promotions work in ordinary variable declarations and pattern variable declarations (see, for example, https://github.com/dart-lang/language/issues/4347#issuecomment-2861859329). So in order to be able to experiment with these possibilities, I want to get rid of this hack. This CL adds a `VariableDeclaration` class, to represent ordinary variable declarations, and modifies the `declare` function (which is used by tests for creating an ordinary variable declaration) so that it creates a `VariableDeclaration`, rather than rewriting it into a `PatternVariableDeclaration` containing a `VariablePattern`. It removes "support" for testing pattern variable declarations that are late or lack an initializer, simplifying `PatternVariableDeclaration.visit`. A few test cases in `type_inference_test.dart` were checking the generated IR for ordinary variable declarations, verifying that it was properly desugared into a pattern variable declaration; these expectations have accordingly changed to no longer expect desugaring. There is no functional change to the compiler or analyzer toolchain. These changes only affect tests in `pkg/_fe_analyzer_shared/test`. Change-Id: I90f074cd6e7a6ed5ed11afadeadb6131ce1d282f Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/432122 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: 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.