[cfe] Run incremental macro tests in separate incremental compilers The way constants are printed using ast-to-text depend on which libraries are available in the component. Because the incremental compiler (by default) only returns the libraries that have been recompiled, the first compilation contains more libraries than the subsequent compilations. Using the same incremental compiler throughout the incremental macro test made the output depend on the order in which the tests were run, which in turn was dependent on the file order in the directory. To avoid this, and to support running individual tests with a stable output, each test is now using its own increment compiler for all the incremental steps within the test. Closes https://github.com/dart-lang/sdk/issues/48558 Change-Id: I37946ed0f940b6644c5efb2b7d167b2a5717f2f3 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/240721 Reviewed-by: Chloe Stefantsova <cstefantsova@google.com> Commit-Queue: Johnni Winther <johnniwinther@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.