| commit | 3cf00938213513dcc16cc845c1c0efc2ea3ddf59 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Mon Dec 30 09:45:59 2024 -0800 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Dec 30 09:45:59 2024 -0800 |
| tree | b27e0571cbf8cd1b8ebc053b727cae73377deba6 | |
| parent | 70c0a2e5f9740c33951fffe4223d9a6f2d7a6f15 [diff] |
[analyzer] Stop implementing some shared types in public API. The following adjustements are made to the analyzer class hierarchy: - `SharedNamedFunctionParameterStructure` is moved from the `implements` clause of `ParameterElement` to the implements clause of `ParameterElementMixin`, a mixin that is used by all concrete subtypes of `ParameterElement`, but which is not part of the analyzer's public API. - `SharedNamedTypeStructure` is moved from the `implements` clause of `RecordTypeNamedField` to the implements clause of `RecordTypeNamedFieldImpl`, the sole concrete subtype of `RecordTypeNamedField`, which is not part of the analyzer's public API. To account for these changes, the analyzer's use of the shared types `FunctionTypeImpl`, `TypeConstraintGenerator`, and `TypeConstraintGeneratorMixin` needed to be adjusted so `ParameterElementMixin` is supplied as a type parameter instead of `ParameterElement`. This required adding a cast to the `FunctionTypeImpl` constructor, which I intend to remove in a future CL. 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: I889b9f87d7d077d10935c4506c454507a480afcd Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/402380 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.