commit | fdb6ca6d0153e47c28d2c7b6471a921a7ca871ce | [log] [tgz] |
---|---|---|
author | Robert Nystrom <rnystrom@google.com> | Tue Mar 30 18:41:21 2021 +0000 |
committer | commit-bot@chromium.org <commit-bot@chromium.org> | Tue Mar 30 18:41:21 2021 +0000 |
tree | 6b23ce74212b9826a90f8b76bb12f7b1f14e6a18 | |
parent | 6c30a7d5828094417bcd2c43c2a5efe4696e387c [diff] |
Add support for context messages to static error tests. Currently only CFE ("Fasta") tests have their context message output parsed. It should be easy to extend that to dart2js and DDC if that's useful. Analyzer might be more work. This also adds support to the test updater for inserting context messages when updating tests. By default, that flag is off, so the existing behavior is preserved where context messages are ignnored. If you want them, pass "-c" when updating a test. When validating test output, if the test file contains context messages, then they are validated. Otherwise, any context messages in the CFE output are ignored. This way existing tests still pass. Change StaticError to represent a single error for a single front end. Before, the data model collapsed errors for different front-ends at the same location into a single StaticError object which tracked different messages for each front end. The idea was to move towards a world where they really are the "same" error with eventually the same message. But this adds a lot of complexity with things like merging errors and doesn't reflect the reality that each error from each front end is basically its own thing. Also, critically, it makes it much harder to attach context messages to a specific front end's error object. This changes it so that an instance of StaticError represents a single error for a single front end. The test file syntax is unchanged and the updated tool behaves the same. In a static error test, multiple expectations can still share the same "// ^^^" marker line. They are just expanded to multiple StaticError objects at parse time. This eliminates all of the complexity around merging and simplifying errors. Change-Id: Ida1736bfcde436fc2d1ce2963d91fa9cb154afa8 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/193281 Commit-Queue: Bob Nystrom <rnystrom@google.com> Reviewed-by: Paul Berry <paulberry@google.com>
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).
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 on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.