Fine. Don't lookup private fields, methods from other libraries. Prevent the resolver from considering private identifiers when collecting applicable extensions for a different library. Previously we probed members by simple name and could end up touching private fields/methods like `_foo` across library boundaries, which led to unnecessary dependency tracking and occasional cache churn (e.g., ID mismatches) and extra analysis work. Add an early accessibility guard: - Skip an extension if the requested `baseName` is not accessible from the extension’s library URI. With this guard in place, the subsequent per-member name equality checks are redundant and are removed, simplifying the lookup. The result is correct privacy behavior, fewer spurious lookups, and more stable analysis results. Change-Id: I063823f29d820377897a406663fe4d612c493f72 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/445343 Reviewed-by: Paul Berry <paulberry@google.com> Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
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 in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.