commit | f58adc5dc3e9ecd9186771a1e62df84372cbcbe4 | [log] [tgz] |
---|---|---|
author | Paul Berry <paulberry@google.com> | Tue Mar 15 22:00:22 2022 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Mar 15 22:00:22 2022 +0000 |
tree | 06a9f98af8c4ffd49d92c282acc13de5a2c5d8f7 | |
parent | b6c5e52af6771762aa593b333fd1185f66674658 [diff] |
Rework heuristic for "fixing" type parameters after downwards inference. Sometimes the upwards inference phase of generic type inference is capable of assigning a more specific type than the downwards inference phase, but we don't want to use the more specific type due to Dart's "runtime checked covariant generics" design. For example, in this code: List<num> x = [1, 2, 3]; x.add(4.0); Downwards inference provisionally considers the list to be a `List<num>`. Without this heuristic, upwards inference would refine the type to `List<int>`, leading to a runtime failure. So what we do is "fix" the type parameter to `num` after downwards inference, preventing upwards inference from doing any further refinement. (Note that the heuristic isn't needed for type parameters whose variance is explicitly specified using the as-yet-unreleased "variance" feature, since type parameters whose variance is explicitly specified don't undergo implicit runtime checks). Previously, this heuristic was implemented in a kludgy way: we would go ahead and gather type constraints during both the upwards and downwards inference phases, and then just prior to choosing the final type, if the downward constaints were sufficient to lock down the type, we would discard the constraints from the upwardsr inference phase. This change simplifies the logic so that we figure out which parameters to fix after the downwards inference phase, and simply stop accumulating constraints for them. This is a preparatory step towards implementing https://github.com/dart-lang/language/issues/731, which will require splitting type inference into more phases. Change-Id: I0cc5774e61a5ace589ea0f45a20fbc1a67c8b940 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/237381 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.