| commit | 0d127497ac6f9895a006e0c3b66203861facaf59 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Fri Dec 13 12:27:21 2024 -0800 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 13 12:27:21 2024 -0800 |
| tree | 7bb59ba898c215d8988f4672bed6289a7ff0911e | |
| parent | c878108cc85b0d36d0888d049abf23c89c30bf4a [diff] |
[analyzer] Change ResolverVisitor to always visit subexpressions using analyzeExpression. Previously, when `ResolverVisitor` needed to provide a context to a subexpression, it would always use `analyzeExpression` to visit it, but when no context was needed, it would sometimes visit the subexpression by calling `ExpressionImpl.accept`. This made the `ResolverVisitor` more difficult to reason about, since there wasn't a common method through which all subexpression visits were dispatched. With change, any time the `ResolverVisitor` visits an expression in a context that's inside a method body or initializer, it visits it using `analyzeExpression`. To make sure I haven't missed anything, and to prevent future regressions, I've added an assertion to `_InferenceLogWriterImpl.enterExpression` that verifies that all expressions visited by the `ResolverVisitor` are visited via `analyzeExpression` when inside a top level declaration. This change paves the way for allowing the analyzer to use the shared implementation of null-shorting introduced in https://dart-review.googlesource.com/c/sdk/+/399480. Change-Id: I56eb102ae0034898f5171ac4cc3e90676bce5db7 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/399781 Reviewed-by: Brian Wilkerson <brianwilkerson@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.