| commit | 9d851a3d91335c90968d9dc66ab39e2cfff6f0ac | [log] [tgz] |
|---|---|---|
| author | Konstantin Shcheglov <scheglov@google.com> | Fri Aug 15 08:58:27 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 15 08:58:27 2025 -0700 |
| tree | 9a97e3d6fa55812723ecb15c0bee07d2882088a5 | |
| parent | 588026e315481eaa13ca7152028de0b87a5850f7 [diff] |
Fine. Record dependencies on accessible extensions. Record dependencies on exported extensions from imported libraries. This allows the analyzer to more accurately invalidate and re-analyze when relevant extensions are added, removed, or modified. Dependencies on separate getters / setters / methods are recorded using already existing mechanism in `InstanceItemRequirements`: `requestedGetters`, `requestedSetters`, `requestedMethods`. Key changes include: - A new `exportedExtensions` property is added to `LibraryManifest` to store the IDs of all declared or re-exported public extensions. - The `accessibleExtensions` getter in `LibraryFragmentImpl` now records a requirement on the `exportedExtensions` of all contributing imported libraries. - A new failure type, `ExportedExtensionsMismatch`, is introduced to handle mismatches in the set of exported extension IDs between analysis cycles. - The `TopLevelNotInterface` failure is replaced by the more general `TopLevelNotInstance` to cover more element types. Change-Id: I6a9aa752a4fd55bdc34fc8886ccde89369fd49ef Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/444480 Reviewed-by: Johnni Winther <johnniwinther@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.