| commit | 74ef6d1740fb6b53715d24aa62b5d5e42d81449f | [log] [tgz] |
|---|---|---|
| author | Sam Rawlins <srawlins@google.com> | Mon Sep 22 14:36:22 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Sep 22 14:36:22 2025 -0700 |
| tree | 6e37540abd15bc429745a28630d03fba41b820b6 | |
| parent | 8875f1a43a7a89e677c7c89d62f62c12b3595e53 [diff] |
DAS plugins: Do not run lint rules or warnings unnecessarily Work towards https://github.com/dart-lang/sdk/issues/61490 When a plugin re-resolves a library [1] via `AnalysisSessionImpl.getResolvedLibrary`, which calls `AnalysisDriver.getResolvedLibrary`, eventually we get down to `LibraryAnalyzer.analyze`. This method contains the singular piece of code that checks `AnalysisOptions.lint` and `AnalysisOptions.warning` [2]. A plugin re-resolves a library in order to parse the code, and ultimately resolve the library into a LibraryElement. It does _not_ use any lint computed by `LibraryAnalyzer.analyze()`, nor any warnings, nor even any compile-time errors. So we should do our best to do the minimal amount of work that still gets us our LibraryElement. Setting `AnalysisOptions.lint` and `AnalysisOptions.warning` reduces the amount of work that `LibraryAnalyzer.analyze()` does. [1]: https://github.com/dart-lang/sdk/blob/c11f9118692461f61570e1ee07b6f5fc43288bb0/pkg/analysis_server_plugin/lib/src/plugin_server.dart#L351 [2]: https://github.com/dart-lang/sdk/blob/c11f9118692461f61570e1ee07b6f5fc43288bb0/pkg/analyzer/lib/src/dart/analysis/library_analyzer.dart#L342-L359 Change-Id: I73413a6646b14ff3a01246470b00e0a3676c4b3a Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/450365 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Samuel Rawlins <srawlins@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.