| commit | d3de420bf81d1639e4f740ccf90746d3b9cc6636 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Fri Feb 14 05:24:22 2025 -0800 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 14 05:24:22 2025 -0800 |
| tree | 4d96ee14a22abe2a31d58b05e01bfd84817e2223 | |
| parent | 4c6326353796ed628b916624264d1bacf0339064 [diff] |
Add a custom lint to sanity check the analyzer public API. The new lint, called `analyzer_public_api`, verifies that the analyzer public API satisfies the following properties: - No method, function, getter, setter, or supertype in the public API refers to a non-public type. - No `export` declaration in the public API shows a non-public name. - No declaration in the public API has a name ending in `Impl`. - No file in the public API has a `part` declaration that points to a file that's not in the public API. (If it did, then the other checks could be circumvented.) A new annotation is added, `@AnalyzerPublicApi()`, allowing declarations in `package:analyzer/src` or `package:_fe_analyzer_shared/src` to be marked as part of the analyzer public API. This is necessary because some parts of the analyzer public API need to be declared elsewhere and then exported by the analyzer. A few lint violations have been ignored using `ignore:` comments. I will try to clean these up in follow-up CLs. Fixes https://github.com/dart-lang/sdk/issues/60058. Bug: https://github.com/dart-lang/sdk/issues/60058 Change-Id: I0047a73dec8a29e2ffe03dd3a90f7e41ca2e27b6 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/409763 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Johnni Winther <johnniwinther@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.