| commit | 922f212340fd10b041a1659c8571a69f3e6f6370 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Fri Dec 06 17:54:50 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 06 17:54:50 2024 +0000 |
| tree | 7458c21b0442451e47ca0e5b100a78b178f23dab | |
| parent | c0d4aa256d116da606d7cd3863d194c1df511f4e [diff] |
[analyzer] Fix null shorting extent in cascade sections.
When a cascade section contains a null-aware expression, the null
shorting should be terminated at the end of the cascade section. For
example, in the statement:
e..x?.f()..g();
if `e.x` evaluates to `null`, the call to `f()` should be skipped, but
not the call to `g()`.
Prior to this fix, the analyzer erroneously considered the null
shorting to be terminated at the end of the entire cascade. The
mistake wasn't easily observed, since the analyzer doesn't have
back-end semantics. But it was still observable in some rare cases
involving type promotion. For example, in the statement:
e..x?.f(i!)..g(i!);
the analyzer would consider the second `!` to be unnecessary, because
in its model of flow control, `g(i!)` would only ever execute after
`f(i!)`.
Fixes https://github.com/dart-lang/sdk/issues/59658.
Bug: https://github.com/dart-lang/sdk/issues/59658
Change-Id: I8540daca121dac6960f8d6a2a3ffa3e38a0bf921
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/398926
Auto-Submit: Paul Berry <paulberry@google.com>
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
Commit-Queue: Paul Berry <paulberry@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
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 in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.