| commit | d41017335322d8156bc0ab33a9c577d9d6683035 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Tue Aug 05 14:14:01 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 05 14:14:01 2025 -0700 |
| tree | ca5bc7b7b991e79a96e2f61523f89a79f959fe8f | |
| parent | f2c73a7a3f0d70a5f73c22d95ef69a68542814e2 [diff] |
Ignore TODOs in analyzer_utilities package. Some time ago, the analyzer team decided to adopt the convention of using `TODO` comments to document long term issues that should persist in the codebase, and `FIXME` comments to document short term issues that need immediate attention. Accordingly, it makes sense to suppress `TODO` comments from being surfaced to the IDE "problems" view (since there can be a lot of them, and they're not immediately actionable). This makes VSCode's "problems" view much more usable in "tree" mode. Previous CLs that have made this change in other packages: - https://dart-review.googlesource.com/c/sdk/+/295662 - https://dart-review.googlesource.com/c/sdk/+/325121 - https://dart-review.googlesource.com/c/sdk/+/358980 - https://dart-review.googlesource.com/c/sdk/+/410060 - https://dart-review.googlesource.com/c/sdk/+/440546 - https://dart-review.googlesource.com/c/sdk/+/442167 Change-Id: I06c0118c7b166a6fad550e8f280f3732734a74e1 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/443633 Auto-Submit: Paul Berry <paulberry@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Konstantin Shcheglov <scheglov@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.