commit | 167cf8e637a94a63a97cf9bff985be6e1e152df7 | [log] [tgz] |
---|---|---|
author | Paul Berry <paulberry@google.com> | Wed Feb 01 18:04:35 2023 +0000 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Feb 01 18:04:35 2023 +0000 |
tree | 35e4c1db8f86b96af4cb9f7005f0cd23d8ec3032 | |
parent | 83539664d996cd08c6d2b011f822e46498cc5dbc [diff] |
Flow analysis: implement type promotions for switch cases that share a body. There are two ways type promotion can occur when switch cases share a body: (1) the scrutinee variable (if any) might be promoted, e.g.: f(Object x) { switch (x) { case int _ && < 0: case int _ && > 10: // `x` is promoted to `int` because both cases promote the // scrutinee variable to `int`. } } (2) explicitly matched variables might be promoted at the time of the match, e.g.: f<T>(T t) { if (t is int) { switch (t) { case var x && < 0: case var x && > 10: // `x` has type `T` but is promoted to `T&int`, because // both declarations of `x` are in a context where the // matched value has type `T&int`. } } } The existing flow analysis logic handles case (1) without any extra work, because those promotions are joined as a natural consequence of the flow control join at the end of matching the cases. However, flow analysis has to do some extra work for case (2), because the two copies of variable `x` are associated with different variable declarations (and hence have different promotion keys). To ensure that the promotions are joined in this case, we need to copy the flow model for the two copies of `x` into a common promotion key prior to doing the flow control join. The bookkeeping necessary to figure out a common promotion key is similar to the bookkeeping for logical-or patterns. Bug: https://github.com/dart-lang/sdk/issues/50419 Change-Id: I9ee4ec5d797dae28099aafbaf34fbbeeee5cd626 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/280201 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Johnni Winther <johnniwinther@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.