| commit | cd26fe29fb639e6e6d1e36e3983a6fe5018d80e9 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Tue Sep 30 08:42:22 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 30 08:42:22 2025 -0700 |
| tree | 32b2fb32fe3c66d45f0497931930cbccb2d650b5 | |
| parent | b53d3b79ba0c4bbf84bf025b3a50310b47f8749c [diff] |
[messages] Consistently use AnalyzerCode to refer to analyzer error codes. Creates a new class `AnalyzerCode`, representing an analyzer error code as a class name and an error name, and consistently uses it in places that previously represented analyzer error codes as simple strings. This change allows for better validation. In follow-up CLs, I will use this as a vehicle for cleaning up the `messages.yaml` files to refer to error codes more consistently. For instance: - Currently, the class name is not specified in all circumstances; I will change this so that it is always specified. This in turn will allow error codes of type other than `ParserErrorCode` to be shared between the analyzer and CFE. - Currently, some parts of `messages.yaml` refer to errors using `UPPER_SNAKE_CASE` while others use `lower_snake_case`. I will change this so that `lower_snake_case` is used consistently. Change-Id: I6a6a696405de7d7e89b1ee11baa776ee639be8fd Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/452460 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: 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.