| commit | 0677dc14cf17029184c12e0f401295773b1d84b8 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Fri Oct 03 10:32:04 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 03 10:32:04 2025 -0700 |
| tree | ea6a501b9ef55ae77d29f3813fba897cdfce3f16 | |
| parent | dfebf912a5ab4f1ecf849e6531b799cdfe9d8002 [diff] |
[messages] Replace remaining CFE analyzerCode values. Replaces the remaining `analyzerCode: FOO` entries in `pkg/_fe_analyzer_shared/messages.yaml` with `psuedoSharedCode: FOO` entries. A `pseudoSharedCode` entry carries two pieces of information: it indicates that the error code is "pseudo-shared" (meaning that there is manually maintained logic that translates it from a CFE diagnostic to an analyzer diagnostic), and it provides an enum value that can be used by the manually maintained logic to identify which analyzer error to translate to. In the few cases where diagnostic had a `pseudoShared: true` annotation but no `analyzerCode`, a fresh `pseudoSharedCode` is introduced. The diagnostic code generation logic is updated accordingly. The logic that translates CFE diagnostics to analyzer diagnostics is also updated. This change carries two benefits: - It more accurately reflects reality; calling these codes `analyzerCode` was inaccurate because there was no automated process to verify that they corresponded to actual analyzer error codes, and in fact in many cases they didn't. - It avoids confusion with the `analyzerCode` values in `pkg/_fe_analyzer_shared/messages.yaml`, which _do_ in fact correspond to actual analyzer error codes. Change-Id: I6a6a69640fe4b04da0296086d052be46126a1ebd Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/453102 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Paul Berry <paulberry@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.