[analyzer] Fix "yield in non-generator" error reporting. The analyzer unit tests `YieldEachInNonGeneratorTest.test_async` and `YieldInNonGeneratorTest.test_async` were marked with a `@FailingTest` annotation that claimed that the tests were failing because the parser was trying to parse the yield statement as a binary expression. The actual reason they were failing was because (a) both the analyzer and the shared parser were redundantly flagging the error, resulting in two errors rather than one, and (b) the tests had an incorrect offset and length for the expected error. As a result of these tests being marked with a `@FailingTest` annotation, we had no test coverage of the `YIELD_EACH_IN_NON_GENERATOR` and `YIELD_IN_NON_GENERATOR` errors. I've resolved the redundancy by suppressing the error from the parser and keeping the analyzer's logic to flag the error, since the analyzer's logic produces a more specific error (it correctly distinguishes between `YIELD_EACH_IN_NON_GENERATOR` and `YIELD_IN_NON_GENERATOR`, whereas the shared parser does not). And I've updated the tests with the correct offset and length for the expected error. So the tests no longer fail and test coverage is restored. Change-Id: Ibbee3329d4699d7e78bec964303e9c9b239f0b8b Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/400140 Auto-Submit: Paul Berry <paulberry@google.com> Commit-Queue: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@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.