Detect changes to and always use the bazel-bin symlink Previously if we found a file was generated using one Bazel configuration, then we'd continue using its path even if a new build with a different configuration was more recent. In other words, we'd use a stale generated file. This commit gives `bazel_watcher.dart` the ability to detect changes to symlinks which means that we'll do a refresh if `blaze-bin` changes (it's already being watch in `context_manager.dart`). But since `binPaths` previously always looked at all the possible "bin paths", even after a refresh we could end up with using the wrong one. So the second change of this commit is to look only at the `blaze-bin` symlink in `findFile` (the symlink is updated by Blaze) to make sure that we pick only the most recent path. This doesn't change `binPaths` itself as it's also used for other purposes. Bug: b/193636339 Change-Id: I641a0c9a5694121435360ca46b275d0b920d2911 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/209701 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.