| commit | 80bc65bb0b529b33023b4e812bd328663609921a | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Sat Jun 17 08:13:20 2023 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Jun 17 08:13:20 2023 +0000 |
| tree | 91838ca0e95584102a5ac634231e5b125b540200 | |
| parent | fda85564387a0b375ac594bc9c08cbd157fef9f4 [diff] |
Flow analysis: add field promotion support for cascades. This change updates the flow analysis support for field promotion (which is not yet switched on by default) so that it supports field accesses inside cascade expressions. The key moving parts are: - The type hierarchy `PropertyTarget` (which is used by the client to tell flow analysis whether the target of a property access is `this`, `super`, or an ordinary expression) now has a new class, `CascadePropertyTarget`, to represent the situation where the target of the property access is an implicit reference to the target of the innermost enclosing cascade expression. - Flow analysis has two new methods on its API: `cascadeExpression_afterTarget` and `cascadeExpression_end`, so that the client can inform flow analysis when a cascade expression is being analyzed. - Flow analysis uses its `_makeTemporaryReference` method to track the implicit temporary variable that stores the target of cascade expressions. (This method was developed as part of flow analysis support for patterns, where it creates the data structures necessary to track the implicit variables that are created as part of pattern desugaring). - The "mini-AST" pseudo-language used by flow analysis unit tests now has a way to represent cascade expressions and method invocations. - In addition to unit tests for `_fe_analyzer_shared`, `analyzer`, and `front_end`, there are new language tests in `tests/language/inference_update_2` to test cascaded field promotions in end-to-end fashion. Bug: https://github.com/dart-lang/language/issues/2020 Change-Id: I21353bbc884ed599cb1739cecfb68ad1d975d18b Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/309220 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Paul Berry <paulberry@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
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.