0b94228695
This change ensures that the only types ever passed to ErrorReporter arguments are String, DartType, int, Uri, or Element. A few call sites had to be changed so that instead of passing in AST nodes they passed in the result of calling `toString` on those AST nodes. In future CLs, I plan to move toward a system where instead of passing the message arguments to ErrorReporter as a list of `Object`, we call a `withArguments` method that's specific to each error; that method will have a specific list of argument types that it supports, so that if we accidentally pass the wrong things into an error message, the problem will be detected at compile time (instead of the user just seeing a confusing error message). The `withArguments` methods will be code generated from annotations in the analyzer's `messages.yaml` file. Keeping the set of types supported by those `withArguments` messages small should help simplify the code generation process, and provide flexibility for how errors are represented in the future. Change-Id: I4a793db2fe5b1344199b770898634b61be41ad11 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/216301 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Daco Harkes <dacoharkes@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> |
||
|---|---|---|
| .dart_tool | ||
| .github | ||
| benchmarks | ||
| build | ||
| client | ||
| docs | ||
| pkg | ||
| runtime | ||
| samples | ||
| samples-dev/swarm | ||
| samples_2 | ||
| sdk | ||
| tests | ||
| third_party | ||
| tools | ||
| utils | ||
| .clang-format | ||
| .gitattributes | ||
| .gitconfig | ||
| .gitignore | ||
| .gn | ||
| .mailmap | ||
| .packages | ||
| .style.yapf | ||
| .vpython | ||
| AUTHORS | ||
| BUILD.gn | ||
| CHANGELOG.md | ||
| codereview.settings | ||
| CONTRIBUTING.md | ||
| DEPS | ||
| LICENSE | ||
| PATENT_GRANT | ||
| PRESUBMIT.py | ||
| README.dart-sdk | ||
| README.md | ||
| sdk_args.gni | ||
| SECURITY.md | ||
| WATCHLISTS | ||
Dart
A client-optimized language for fast apps on any platform
Dart is:
-
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
-
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
-
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
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).
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 on our wiki.
Contributing to Dart
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.