| commit | 111e84b958b19325160b7e0b1b9e20eed9fca650 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Mon Aug 04 11:20:23 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 04 11:20:23 2025 -0700 |
| tree | 9441dec3b6ec21e2e91f42697a6619bab4e22b10 | |
| parent | c237ac8e23307eecf781feb8c2feefb633f48ef4 [diff] |
Rename CFE DiagnosticMessage class. The analyzer already has a class with the same name, but a slightly different purpose. (The analyzer's class represents a single message associated with a source location, whereas the CFE's class represents a message along with related context messages). I'm currently embarking on an arc of work that I hope will eventually culminate in unifying the analyzer and CFE diagnostic message representations into a single set of classes. Until that unification is complete, both representations will have to co-exist in the `_fe_analyzer_shared` package. To reduce confusion during that time period, I would like the classes to have distinct names. Since the analyzer's `DiagnosticMessage` class is exposed through the analyzer public API, analyzer clients may depend on the name. So it makes sense to rename the CFE's `DiagnosticMessage` class. Tested: standard trybots Change-Id: I6b6948fe9da18c7b6688333fa12ffeea8e81436f Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/441831 Reviewed-by: Alexander Markov <alexmarkov@google.com> Reviewed-by: Ömer Ağacan <omersa@google.com> Reviewed-by: Nicholas Shahan <nshahan@google.com> Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Johnni Winther <johnniwinther@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.