[analyzer] Add name and token to ExpectedType enum. Changes the analyzer's `ExpectedType` enum (which is used for runtime type checks of parameters to diagnostic messages) so that it includes the types `name` and `token`. These correspond with types used in parser error reporting. In a future CL, I will be adding `parameters` declarations to `pkg/front_end/messages.yaml`, following a similar format to the format used by `pkg/analyzer/messages.yaml`. When that happens, the analyzer's diagnostic message code generator will start trying to generate runtime type checking code for parameters of type `name` and `token`. Landing this change now ensures that when the new runtime type checking code gets generated, it will work properly. Change-Id: I6a6a69648c2fdff63d93da5c5c39ba75f65edc9c Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/448248 Reviewed-by: Konstantin Shcheglov <scheglov@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.