[messages] Make derived classes for CfeStyleErrorCodeInfo.

Changes `CfeStyleErrorCodeInfo` to an abstract class and makes two
derived classes with additional integrity checks:

- `FrontEndErrorCodeInfo`, to represent error codes from
  `pkg/front_end/messages.yaml`. The constructor for this class checks
  that the message doesn't have an `index` field (because messages
  with an `index` field are meant to be shared, and thus should go in
  `pkg/_fe_analyzer_shared/messages.yaml`).

- `SharedErrorCodeInfo`, to represent error codes from
  `pkg/_fe_analyzer_shared/messages.yaml`. The constructor for this
  class checks that the message _does_ have an `index` field, and also
  checks that its `analyzerCode` field contains exactly one entry
  (this is important because it determines the name of the analyzer
  error that will be generated from the shared error definition).

Also, renames `CfeStyleErrorCodeInfo.analyzerCode` to `analyzerCodes`
(since, in general, there may be more than one associated analyzer
error code) and adds `SharedErrorCodeInfo.analyzerCode` to fetch the
one analyzer error code associated with a shared error.

These changes have the effect of baking the assumptions about front
end and shared error codes into the type system, which should make it
easier to write code that depends on those assumptions. In follow-up
CLs, I plan to modify the code generation logic in ways that rely more
heavily on these assumptions, and having them baked into the type
system will make that more straight forward.

Change-Id: I6a6a696444ae6695cc9548cb087488a4464e4777
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/449605
Commit-Queue: Paul Berry <paulberry@google.com>
Reviewed-by: Johnni Winther <johnniwinther@google.com>
4 files changed
tree: d21f2803ca2ac9445e76d15dc74541708a2d1342
  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.