[analyzer] Use TypeParameterElementImpl2 when interfacing with shared code. Change the analyzer's use of the following shared generic types so that it supplies the type parameter `TypeParameterElementImpl2` instead of `TypeParameterElement` as the type it uses to represent type parameters: - `GeneratedTypeConstraint` - `MergedTypeConstraint` - `SharedFunctionTypeStructure` - `SharedInferenceLogWriter` - `SharedInferenceLogWriterImpl` - `TypeAnalyzer` - `TypeAnalyzerOperations` - `TypeConstraintFromArgument` - `TypeConstraintFromExtendsClause` - `TypeConstraintFromFunctionContext` - `TypeConstraintFromReturnType` - `TypeConstraintGenerator` - `TypeConstraintGeneratorMixin` - `TypeConstraintOrigin` - `UnknownTypeConstraintOrigin` This required adding type casts in a few places. In other places, I avoided type casts by tightening up some return types (for example, `InstanceElementImpl2.typeParameters2` now returns `List<TypeParameterElementImpl2>` instead of `List<TypeParameterElement2>`. The analyzer public API was unchanged, though (for example, `InstanceElement2.typeParameters2` still has a return type of `List<TypeParameterElement2>`), so clients should be unaffected. As a result of this change, it is no longer necessary for a public API class to implement the shared interface `SharedTypeParameterStructure`. This interface was previously implemented by `TypeParameterElement`; it is now implemented by `TypeParameterElementImpl2`, which is not a part of 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: Ic6d42b415620430210e25ed212b11e03851d25ed Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/402500 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.