| commit | 08154451d592311947a9cbe025238892efd3f320 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Thu Apr 03 11:56:51 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 03 11:56:51 2025 -0700 |
| tree | 5be21f6750aad443bed7b43d4602fe45aa69189f | |
| parent | 437bf924a718f26a65bf277b31df2c6b8df76ae5 [diff] |
[_fe_analyzer_shared] Use TypeAnalyzerOptions to configure flow analysis. Previously, flow analysis was configured by passing a set of named booleans to its constructor, each to enable or disable a separate language feature. This change merges the flow analysis configuration with the `TypeAnalyzerOptions` class (which was already being used for configuring the shared `TypeAnalyzer` class). This should make it easier to add language features to the shared code base in the future, since there will be one common place where all features will be configured. To avoid duplicating the logic that creates `TypeAnalyzerOptions`, I've had to do a bit of minor surgery to the clients: - In the test harness in `_fe_analyzer_shared`, there is a common method (`Harness.computeTypeAnalyzerOptions`) that constructs `TypeAnalyzerOptions` based on the harness configuration. It is called from a few different tests. - In `pkg/analyzer`, there is a common method (`computeTypeAnalyzerOptions`) that constructs `TypeAnalyzerOptions` based on a `FeatureSet`. It is used by `LibraryAnalyzer.analyzeForCompletion`, `LibraryAnalyzer._resolveFile`, and the late variable `AstResolver._typeAnalyzerOptions`. - In `pkg/front_end`, I've moved computation of `TypeAnalyzerOptions` from the `InferenceVisitorImpl` constructor to the `TypeInferrerImpl` constructor; the options are then passed to the `InferenceVisitorImpl` by `_createInferenceVisitor`. I'm doing this work now as preparation for adding support for sound flow analysis (https://github.com/dart-lang/sdk/issues/60438), so that I can add the logic to enable it in a clean way. Bug: https://github.com/dart-lang/sdk/issues/60438 Change-Id: Ib845194adb404b4c0a3feeff17a14ae641d515eb Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/419940 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Paul Berry <paulberry@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.