[CFE] Make macros work when initializing from dill Previously, when initializing from dill, if the dill we initialize from has a macro in it (and we don't remove it because of invalidation) the macro system would think it was a precompiled dill and thus not compile it as something it could use for running macros. Then when it tried to use it, it would figure out it didn't have it (and crash). This CL fixes the issue by reworking the logic: * Assume the platform is there (dart: uris) * Assume the uris given specifically as precompiled (and not removed because of invalidation in/by the incremental compiler) is there. No tests are added, but it has been manually tested in flutter. Change-Id: Ica6c4f2f0601334d50beccdd7cf9d5740e611384 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/239026 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.