[front_end] Pass all diagnostic arguments to Message.arguments prior to conversion.

Previously, most entries in the `Message.arguments` map directly
reflected the values passed to `withArgumentsOld` (prior to converting
and the arguments into a form more suitable for display), but there
were some exceptions:

- For `name`, `name2`, `name3`, and `name4` parameters, the entry in
  `Message.arguments` was the value of the name after passing it
  through the function `demangleMixinApplicationName`.

- For `nameOKEmpty`, the entry in `Message.arguments` was the value of
  the name after substituting `(unnamed)` for the empty string.

- For `stringOKEmpty`, the entry in `Message.arguments` was the value
  of the name after substituting `(empty)` for the empty string.

This CL changes the generated `withArgumentsOld` functions so that all
the values in `Message.arguments` uniformly directly reflect the
values passed to `withArgumentsOld`.

In practice this has no user-visible effect, because the only use of
`Message.arguments` outside of testing is to convert parser
diagnostics to analyzer form, and none of the above conversions have
any effect on parser diagnostics. (This is because (a) mixin name
mangling happens after the parsing stage, and (b) the parser
diagnostics don't use `nameOKEmpty` or `stringOKEmpty` parameters.)

In follow-up CLs, I plan to rework the code generator for
`withArgumentsOld` so that it's easy to generate a parallel
`withArguments` function that takes named arguments. Starting from a
more uniform behavior will make that rework easier.

Change-Id: I6a6a69642e1d9b8277c4959d4a9c2d5ae0cd5b8f
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/447627
Reviewed-by: Johnni Winther <johnniwinther@google.com>
Commit-Queue: Paul Berry <paulberry@google.com>
3 files changed
tree: bb261073101abeefabeb02f5f49be7c71ca3fa79
  1. .dart_tool/
  2. .github/
  3. benchmarks/
  4. build/
  5. docs/
  6. pkg/
  7. runtime/
  8. samples/
  9. sdk/
  10. tests/
  11. third_party/
  12. tools/
  13. utils/
  14. .clang-format
  15. .gitattributes
  16. .gitconfig
  17. .gitignore
  18. .gn
  19. .mailmap
  20. .style.yapf
  21. AUTHORS
  22. BUILD.gn
  23. CHANGELOG.md
  24. codereview.settings
  25. CONTRIBUTING.md
  26. DEPS
  27. LICENSE
  28. OWNERS
  29. PATENT_GRANT
  30. PRESUBMIT.py
  31. pubspec.yaml
  32. README.dart-sdk
  33. README.md
  34. sdk.code-workspace
  35. sdk_args.gni
  36. sdk_packages.yaml
  37. SECURITY.md
  38. WATCHLISTS
README.md

Dart

An approachable, portable, and productive language for high-quality apps on any platform

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 platforms illustration

License & patents

Dart is free and open source.

See LICENSE and PATENT_GRANT.

Using Dart

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).

Building Dart

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.

Contributing to Dart

The easiest way to contribute to Dart is to file issues.

You can also contribute patches, as described in Contributing.

Roadmap

Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.