| commit | 3e23d1d4dd57de4f64e2190f40765eab221ee436 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Fri Oct 17 07:56:50 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 17 07:56:50 2025 -0700 |
| tree | 643752b4b1305a8d6d15e5c2996faeb8ca0f7c87 | |
| parent | 081f93dc67cadb8e198682105b4146c3ff6500bb [diff] |
[messages] Disambiguate recordLiteralOnePositionalNoTrailingCommaByType. Renames the diagnostic code `CompileTimeErrorCode.recordLiteralOnePositionalNoTrailingComma` to `CompileTimeErrorCode.recordLiteralOnePositionalNoTrailingCommaByType`. This avoids an ambiguity between this message and `ParserErrorCode.recordLiteralOnePositionalNoTrailingComma`. The two messages need to stay distinct, because one is reported during parsing, and the other is reported during type analysis. Only `ParserErrorCode.recordLiteralOnePositionalNoTrailingComma` should prevent the formatter from running. Avoiding ambiguities like these is important, because in many cases the user only sees the diagnostic name; they don't see the class it's in. For example, `ignore:` comments just give the diagnostic name, and the web page https://dart.dev/tools/diagnostics only shows diagnostic names. In the future I intend to add an error check to the analyzer diagnostic code generator, to ensure that there are no ambiguities like these. This CL is a prerequisite for adding the error check. Note that the `sharedName` of the renamed diagnostic remains `RECORD_LITERAL_ONE_POSITIONAL_NO_TRAILING_COMMA`, so there will be no change in how the error is presented to the user. Change-Id: I6a6a6964c1d4e28c6db71072252abf95fbc13206 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/455562 Reviewed-by: Johnni Winther <johnniwinther@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@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.