commit | 61f1d6910773225ebddcaf1fd0fc1837fea588cf | [log] [tgz] |
---|---|---|
author | Paul Berry <paulberry@google.com> | Wed Dec 25 07:09:35 2024 -0800 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Dec 25 07:09:35 2024 -0800 |
tree | f88d5a84bb5613e295e4ccea47f420a666e6addd | |
parent | d2f3470d410c9d6788d21321f8610f08df19b23b [diff] |
[analyzer] Stop implementing SharedFunctionTypeStructure in analyzer public API. When I introduced the `SharedFunctionTypeStructure` class in https://dart-review.googlesource.com/c/sdk/+/386322, I failed to realize that a side effect of this change was to expose the shared methods `positionalParameterTypes`, `requiredPositionalParameterCount`, and `sortedNamedParameters` through the analyzer's public API. To correct that mistake, I've moved the reference to `SharedFunctionTypeStructure` from the `implements` clause of `FunctionType` to the `implements` clause of `FunctionTypeImpl`. To avoid this change causing a breakage for clients, I've also added deprecated declarations of these three getters to the `FunctionType` class. This ensures that if any analyzer clients have already started depending on them, their code will continue to work, but they'll be alerted to the fact that the members will be removed in the future. 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. Bug: https://github.com/dart-lang/sdk/issues/59763 Change-Id: I442cbe29ed938ec2fed3a3fa65a95c9f0f47a38d Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/401921 Reviewed-by: Brian Wilkerson <brianwilkerson@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.