| commit | 2619f377ab66706af379aec7e18556bbcf2475c7 | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Tue Feb 03 07:18:33 2026 -0800 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 03 07:18:33 2026 -0800 |
| tree | c8302d33295ca8b88a688b10a2118443ccec1432 | |
| parent | 3c4eaf426348579dce409b510ebf244b6ef20cfb [diff] |
[messages] Stop using withArgumentsOld, batch 19. This is one of several planned batches of changes to transition the front end (and related packages) away from the old `withArgumentsOld` diagnostic reporting method, and to the new `withArguments` method. The difference between the two is that `withArguments` has named parameters rather than positional ones, so (a) it's less likely for parameters to be mixed up, and (b) it's compatible with the calling conventions used by analyzer diagnostics. As part of this transition, I'm taking the opportunity to rename the parameters themselves (since the names previously were restricted to a very small set of possibilities based on type), and to document them in `messages.yaml`. To avoid fatigue (both for myself and code reviewers), I've chosen to break the change into many smaller batches. The only changes in this CL that were manually written are those in `messages.yaml`. The others were produced by running the standard diagnostic message code generator and then running the script `use_new_with_arguments.dart`. Change-Id: I6a6a6964e11855686b3f5c888f07a868919005d5 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/477181 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.