| commit | abd4e7754c6036c7fda47460ce0e9e06c5b1990d | [log] [tgz] |
|---|---|---|
| author | Sam Rawlins <srawlins@google.com> | Thu May 08 16:10:57 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 08 16:10:57 2025 -0700 |
| tree | d802722d24cfe1a81b64d863be4782e1e0ff81c9 | |
| parent | 3ef77d1247afb95d75161a4f7a16220db31431f3 [diff] |
Introduce two subclasses of 'LintRule' for handling multiple lint codes Before this change, we had an enforcement that either 'get lintCode' or 'get lintCodes' is implemented, but it was a runtime enforcement. And it was a little roundabout. The new system is simpler and more typical: * `AbstractLintRule` is the parent type, and it's sealed. It provides `get lintCodes` as an interface. Code outside of the lint rules requires this getter, in registering codes, etc. * `LintRule` is the new subclass which is the "90% case." It declares a `get lintRule`, and offers simpler reporting methods for reporting a single code everywhere. * `MultiLintRule` is the new subclass which represents that last "10% case." It only declares the reporting methods which all require a LintCode parameter, since there is no concept of a "default lint code among all my lint codes." Work towards https://github.com/dart-lang/sdk/issues/50986 Change-Id: I63cbbfc1d936bb4428aa0b8f5fb0638c9b61b3dc Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/426284 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@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.