| commit | 85f9e454346d84e4d2d970a95c7d0c163fceafba | [log] [tgz] |
|---|---|---|
| author | Sam Rawlins <srawlins@google.com> | Tue Jul 02 15:22:28 2024 +0000 |
| committer | Samuel Rawlins <srawlins@google.com> | Tue Jul 02 15:22:28 2024 +0000 |
| tree | c1f37c97bb699c1fdbcc972de7188456e7062a15 | |
| parent | aedaede1eb0db28d746f1e1787f81c46b62b2794 [diff] |
linter: Mark 'errors'-related rules with finer-grained categories Work towards https://github.com/dart-lang/linter/issues/4991 Here I just take all of the existing rules marked with `Category.errors` (which are not removed or deprecated), and re-examine what category or categories they fall into. I add new categories: * "binary size" (not super accurate for JS-compile apps, but "binary" is still a common industry term for the JS app that is delivered to the browser) * "documentation comment maintenance" * "error-prone" * "language feature usage" * "memory leaks" (note, different from "binary size"; mostly memory-leak related but may contain other things?) * "non-performant" * "unintentional" * "unused code" For multiple rules, I considered adding a "best practices" category too, but this also seems tragically vague. But for rules like "control_flow_in_finally", "avoid_catches_without_on_clauses", etc. Cq-Include-Trybots: luci.dart.try:flutter-analyze-try,analyzer-win-release-try,pkg-win-release-try Change-Id: I043a509120e7347283d6ab10e8eb73859830abc0 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/371921 Reviewed-by: Marya Belanger <mbelanger@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@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.