[front_end] Rework diagnostic code generation. This change reworks the logic for generating the files `pkg/_fe_analyzer_shared/lib/src/messages/codes_generated.dart` and `pkg/front_end/lib/src/codes/cfe_codes_generated.dart`. The following changes are made: - The generated code is changed so that each `withArgumentsOld` function forwards to a corresponding `withArguments` function, which accepts named arguments rather than positional ones. In later CLs these new `withArguments` functions will be made available to call directly from CFE code. - The code in the `withArguments` functions uses a uniform naming convention, where the parameter names match the parameter names specified in the error message templates, and the variables holding the result of string conversions are named by appending `_0` to the parameter names.* *In principle, variables suffixed with `_1`, `_2`, etc. might be generated in the circumstance where a single parameter gets converted to strings in multiple ways. But this doesn't happen in practice. - The code in the `withArguments` functions converts arguments to strings in a uniform way, by calling either top level functions in `pkg/_fe_analyzer_shared/lib/src/messages/conversions.dart` or methods on the `TypeLabeler` class. - The code generation logic in `pkg/front_end/tool/generate_messages_lib.dart` has been refactored considerably, with an eye toward allowing it to be further generalized in the future. In particular, in follow-up CLs I plan to allow each error message to define the precise set of placeholders it will use, and their types, as is done in the analyzer's `messages.yaml` file. There is no change to functionality. Change-Id: I6a6a69644e3bd3a5871bc4d156865f2ac499e8a6 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/447823 Reviewed-by: Johnni Winther <johnniwinther@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.