| commit | f180b7037c0d1a566e4cdae0d408dc3dc47729b1 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Sun Jun 04 19:40:37 2023 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sun Jun 04 19:40:37 2023 +0000 |
| tree | d1671e45867f899b9e3def97ca91df60dd9074cf | |
| parent | 5e5fe2aa773a25697fa70e39fc57d305289174a0 [diff] |
Shared analysis: remove bogus support for late variable patterns. When I was first developing the shared analysis logic for patterns, I imagined that ordinary variable declaration statements would eventually be re-interpreted as pattern variable declarations, where the pattern was simply a variable pattern. In order to facilitate this, I added support for late variable patterns, so that a decalration of a late variable could be interpreted as a pattern variable declaration where the pattern was a "late variable pattern". In the final implementation, however, this functionality never got used, except in flow analysis unit tests. Both the analyzer and the CFE continue to use their old logic for analyzing ordinary variable declarations (including late variable declarations), and only invoke the shared logic when the declaration in question is truly a pattern variable declaration. In retrospect I believe this is the right approach; ordinary (non-patterned) variable declarations are common enough that it makes sense to have separate logic for analyzing theem; invoking the full generality of pattern variable declarations would simply waste CPU cycles. So this CL removes support for late variable patterns from the shared implementation; this will make future refactoring of flow analysis logic easier. Since the flow analysis unit tests *were* taking advantage of the shared logic for late variable patterns, I had to add some separate logic to the tests to replicate the old functionality when analyzing an ordinary late variable declaration. This new logic is only used in tests. Change-Id: If51efab3c63bdc20d1f2772c2d2dd1e3f487bb00 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/307183 Reviewed-by: Konstantin Shcheglov <scheglov@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.