commit | 4ec71ad43b043975f91e04535c95d35ba13bb402 | [log] [tgz] |
---|---|---|
author | Johnni Winther <johnniwinther@google.com> | Wed Nov 02 10:45:52 2022 +0000 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 02 10:45:52 2022 +0000 |
tree | 89222daf494d5e9a635de2009d81233e7c711ae2 | |
parent | 1d7014c17b570f8f4dec364f6559b6e1d853b903 [diff] |
[cfe] Visit all nodes during top-level inference This changes the way the CFE perform top level inference. Previously the inference would try to visit only the nodes needed to compute the resulting type. In particular, statements (for instance inside function expressions) would never be visited during top level inference. This approach didn't match the analyzer approach which always visits the whole field initializer, including any function expressions. This has lead to various issues in the wild: https://github.com/dart-lang/sdk/issues/49528 https://github.com/dart-lang/sdk/issues/50351 And triggered the language issue: https://github.com/dart-lang/language/issues/1650 While the old CFE approach allowed for more complex field initializers, without reporting a cyclic dependency, for instance var f = () { f(); }; it didn't fit well with the horizontal inference introduced in the 'inference-update-1' feature, since this relies on full inference of function expressions. For instance for T method<T>(T Function(String?) f) { ... } var a = method((o) => o?.length ?? 0); var b = method((o) => o != null ? o.length : 0); var c = method((o) { return o?.length ?? 0; }; the CFE wouldn't infer same type for `a`, `b` and `c`. Furthermore it would skip the condition `o != null` in `b` because it "didn't need the type" (it is known to be `bool`), missing that the condition promotes `o` to non-nullable in the true branch, leading to reporting an error on `o.length` for being a potentially nullable access. For these reasons, the CFE is now changed to _always_ visit the whole field initializer, during top-level inference, making it align itself with the analyzer implementation. Closes #49528 Change-Id: Ic409b42699bb0e986f9d041ccb894863c952edf7 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/267061 Reviewed-by: Chloe Stefantsova <cstefantsova@google.com> Commit-Queue: 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.