| commit | 7198fb9bacfbdb2611a75802bf7ef5074539d4b1 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Sun Jan 19 15:18:19 2025 -0800 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sun Jan 19 15:18:19 2025 -0800 |
| tree | 4d3286ea4b0720c07fe0ac23e19b86679087f41a | |
| parent | eb691963f0181a694b0e705c7bce159eba75bb84 [diff] |
[analyzer] Use TypeImpl for context types. The signatures of `ExpressionImpl.resolveExpression` and all of its overrides are changed so that they expect a context which is a `TypeImpl` rather than a `DartType`. The signatures of expression `visit` methods in `ResolverVisitor` are changed in a similar way. To reduce the number of casts that this introduces, several fields and methods in the following classes have their types changed to use "Impl" types: - `ElementResolver` - `FunctionExpressionInvocationResolver` - `GenericFunctionInferenceTest` - `GenericInferrer` - `InstanceCreationExpressionResolver` - `InterfaceElementImpl` - `InterfaceElementImpl2` - `InterfacesMerger` - `InterfaceTypeImpl` - `InvocationInferenceHelper` - `InvocationInferrer` - `MethodElementImpl2` - `MethodInvocationResolver` - `MixinElementImpl` - `MixinElementImpl2` - `NamedTypeResolver` - `ResolutionReader` - `ResolverVisitor` - `Substitution` - `TypedLiteralResolver` - `TypeSystemImpl` - `_ClassInterfaceType` - `_LiteralResolution` - `_MixinInference` This is part of a larger arc of work to change the analyzer's use of the shared code so that the type parameters it supplies are not part of the analyzer public API. See https://github.com/dart-lang/sdk/issues/59763. Change-Id: I11d476d712846c28b05e0fa1a5972fb7585e114a Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/405101 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.