commit | 9ff5ac12c6efec99b8d6580c7a7154bb5e265add | [log] [tgz] |
---|---|---|
author | Michal Terepeta <michalt@google.com> | Mon May 03 07:35:58 2021 +0000 |
committer | commit-bot@chromium.org <commit-bot@chromium.org> | Mon May 03 07:35:58 2021 +0000 |
tree | 8629204ae7951d416066a2348bd4e97f5bc22819 | |
parent | 7ef0841386f52a555b4b1f7a3cf325b00ab4ea23 [diff] |
React when Bazel/Blaze prefix changes Previously if no Bazel/Blaze symlinks were present, we defaulted to the `bazel-*` ones and never checked if that assumption was accurate. This change starts watching the symlinks and recreates the analysis contexts if a symlink gets added. This way we'll run the `BazelWorkspace` code again and use the correct paths. This is quite important since `bazel/blaze clean` does remove the symlinks so if the analysis server starts at such a point, we would never find any generated files if the workspaced turned out to be a Blaze one. Bug: http://b/175087705 Change-Id: If7bb21c7d69a3092832c18004691d56949e5af54 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/197540 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Michal Terepeta <michalt@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.