[CFE] Don't try to format textual outline result from source with errors Currently we don't get any failures from trying to format erroneous code because we ignore formatting errors if there is an experimental feature enabled, and the "inline class" experimental feature is always forcefully enabled in testing. With that experiment getting enabled (https://dart-review.googlesource.com/c/sdk/+/335062) tests will start failing because nothing stops us from formatting the erroneous code (and nothing asks us to allow failures when we try). This CL instead gives the test access to the needed information (i.e. if there were parse errors or not), and won't try for format the code if there is. Change-Id: I2664cc544a9def9fad3058f6c80c130b8b6b6b4c Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/335448 Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Jens Johansen <jensj@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.