| commit | a8b8df2e457ac1e63400d4875f2b0a6e1c8bf2f0 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Mon Jan 06 06:12:22 2025 -0800 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 06 06:12:22 2025 -0800 |
| tree | c0453e447f9bcfc5bfae46fc451c4d6c50a3e037 | |
| parent | df1df58988fc6bfbd7e19da3cafecb5bf20bd7dc [diff] |
[_fe_analyzer_shared] Renames to prepare for analyzer refactoring. The following shared getters are renamed so that their names are distinct from the corresponding getters in the analyzer: - `SharedFunctionTypeStructure.sortedNamedParameters` is renamed to `sortedNamedParametersShared` to be distinct from the analyzer's getter `FunctionTypeImpl.sortedNamedParameters`. - `SharedFunctionTypeStructure.typeFormals` is renamed to `typeParametersShared` to be distinct from the analyzer's getter `FunctionTypeImpl.typeFormals`. - `SharedNamedFunctionParameterStructure.name` is renamed to `nameShared` to be distinct from the analyzer's getter `ParameterElement.name`. - `SharedNamedTypeStructure.name` is renamed to `nameShared` to be distinct from the analyzer's getter `RecordTypeNamedFieldImpl.name`. These renames pave the way for switching the analyzer's use of these shared types over to the new element model. They're necessary because when the analyzer switches over to the new element model: - `FunctionTypeImpl.sortedNamedParameters` will no longer have the correct type to override `SharedFunctionTypeStructure.sortedNamedParameters`; instead, it will be necessary to convert each named parameter to a corresponding element in the new element model (`FormalParameterElementImpl` or `ParameterMember`). - `FunctionTypeImpl.typeFormals` will no longer have the correct type to override `SharedFunctionTypeStructure.typeParametersShared`; instead, it will be necessary to use `FunctionTypeImpl.typeParameters` (which is a list of new element model type parameters). - `ParameterElementMixin` will no longer implement `SharedNamedFunctionParameterStructure`; instead, `FormalParameterElementImpl` and `ParameterMember` (which are classes in the new element model) will implement it. The class `FormalParameterElementImpl` deliberately doesn't have a `name` getter; instead it has a `name3` getter, with slightly different semantics (it returns `null` rather than the empty string when there is no name). Change-Id: I629e45b6fc588e6a86f7590aab853064e31ab661 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/402220 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Reviewed-by: Chloe Stefantsova <cstefantsova@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.