Import path as p, in Workspace impl libraries In package_build.dart, there are several spots (builtFile(), builtPackageSourcePath(), ...) where `context` is called, in cases where I imagine the author thought there was a class member at hand (as is the case with PackageBuildPackageUriResolver), but these locations are actually using the top-level const `context` from the path package. I think it is super confusing to have class members, and local variables, that shadow an imported top-level const. Better to import with a prefix. Additionally, I unified relative/absolute checking in these files as assert() calls, with helpful messages. Change-Id: I6d409636dab41959cabf392c80f64c4ec5270f7b Reviewed-on: https://dart-review.googlesource.com/c/82560 Commit-Queue: Samuel Rawlins <srawlins@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Dart is an open-source, scalable programming language, with robust libraries and runtimes, for building web, server, and mobile apps.
Visit the dartlang.org to learn more about the language, tools, getting started, and more.
Browse pub.dartlang.org for more packages and libraries contributed by the community and the Dart team.
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.