| commit | 751fe131e923b55f18e05c003134d9f1c36f2494 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Tue Jan 21 10:46:52 2025 -0800 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 21 10:46:52 2025 -0800 |
| tree | 7e668ad5e7aac3c96c88ee26538d25e74fccb119 | |
| parent | cf09edd35e780cdcb38e599327bd9164c87d54a8 [diff] |
[analyzer] Use TypeImpl for type annotation types. The types of `TypeAnnotationImpl.type`, and the fields that override it, are changed from `DartType?` to `TypeImpl?`. Also, the type of `TypeAnnotationExtension.typeOrThrow` is changed from `DartType` to `TypeImpl`. To reduce the number of casts that need to be added, the following changes are made in parallel: - An additional extension `TypeAnnotationImplExtension.typeOrThrow` is added; this has the same behavior as `TypeAnnotationExtension.typeOrThrow`, but it doesn't require a type cast. - Some field types, getter types, method return types, and method parameter types are changed to `Impl` types in the following classes: - `AstRewriter` - `EraseNonJSInteropTypes` - `ExtensionTypeErasure` - `FreshTypeParameters` - `FullInvocationInferrer` - `FunctionExpressionInvocationResolver` - `FunctionReferenceResolver` - `FunctionTypeBuilder` - `InstanceCreationInferrer` - `InvocationExpressionInferrer` - `InvocationInferrer` - `NamedTypeBuilder` - `NamedTypeResolver` - `ResolutionReader` - `TypeAliasElementImpl` - `TypeAliasElementImpl2` - `TypeImpl` - `TypeParameterElementImpl` - `TypeSystemImpl` There is no change to the analyzer public API. 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: I7f753508b53f6744677fd18f66858d70eb974093 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/405221 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@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.