| commit | cc6ef3afdc12b4fc83f79b1a37d13957422822a9 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Mon Dec 09 23:30:17 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Dec 09 23:30:17 2024 +0000 |
| tree | 16a49a5ddb3456bde52f40488ea824a4eeb5a66c | |
| parent | f5d61441cea1f43370408adf1b44adde89820059 [diff] |
[analyzer] Avoid call from one visit method to another in resolver. When `PrefixedIdentifierResolver.resolve` rewrites a prefixed identifier expression to a property access (which it does when the prefix is an expression having record type), instead of making a call from `ResolverVisitor.visitPropertyAccess` to `ResolverVisitor.visitPropertyAccess` to resolve the rewritten expression, use a private helper method for both code paths. This ensures that all `visit` methods in the `ResolverVisitor` are called solely from `ExpressionImpl.accept` or from `ExpressionImpl.resolveExpression` (at least as far as expressions are concerned). This will pave the way for a follow-up CL, in which I will make sure that all expression resolution is done through the `TypeAnalyzer.analyzeExpression` method. That will in turn allow the analyzer to use the shared implementation of null-shorting introduced in https://dart-review.googlesource.com/c/sdk/+/399480. Change-Id: I782e10be2f58fdc0991b6d917f81bedd856485a9 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/399627 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.