| commit | 7968ea8b1f5ffee7193b5b6388858e6104378bc7 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Thu May 11 20:58:22 2023 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 11 20:58:22 2023 |
| tree | f30c16454098d30d4d63d450486915b258654e1e | |
| parent | f4bd3590fc5c2b0d6a4961c89761b0bae508253d [diff] |
Remove unused parameter and return value from `handleCaseHead`. These were introduced in https://dart-review.googlesource.com/c/sdk/+/287601 to allow the common front end to report back to the shared analysis logic when it desugars a guard expression, so that flow analysis will properly account for any promotions made by the guard expression; previously, if a guard expression got desugared by the front end, promotions performed by the guard would be lost. In https://dart-review.googlesource.com/c/sdk/+/298840, we've switched to a more general technique for ensuring that promotions performed by the guard will not be lost: now the `dispatchExpression` method uses `FlowAnalysis.forwardExpression` to compensate for the differences in the conventions of the CFE and the shared logic, so that the shared logic no longer needs access to the desugared expression. So the `head` parameter (and the associated return value) are no longer needed. In a future change, I plan to adjust the CFE conventions to match those of the shared logic, so that `FlowAnalysis.forwardExpression` won't be needed at all (see https://github.com/dart-lang/sdk/issues/52189). Change-Id: I686d1d5b7e4c9db353f583c38792274451f9f8bb Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/302366 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.