| commit | 41e983db813a5af0122fd903694ccb9829df5bcf | [log] [tgz] |
|---|---|---|
| author | Konstantin Shcheglov <scheglov@google.com> | Fri Sep 05 12:19:26 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 05 12:19:26 2025 -0700 |
| tree | 15cee85d8b35a5f43e802d3b2c682ffd44f490d9 | |
| parent | acc4ee0b1e3fc94a25bdf24431e7567e20cc663d [diff] |
Fine. Track hasNonFinalField in manifests and requirements. Persist and track `hasNonFinalField` for interface-like elements so fine- grained dependencies can invalidate precisely when a class (or its supertypes) declares a non-final instance field. What’s changed - Store `hasNonFinalField` on manifest items for classes, enums, extension types, and mixins. The flag is serialized/deserialized and printed in dumps. - Add a tracked getter on `InterfaceElementImpl` that records a dependency when `hasNonFinalField` is queried; use a private backing field with a setter. - Extend requirements schema with an optional `hasNonFinalField` entry and record it when requested. - Validate the requirement via a new `InterfaceHasNonFinalFieldMismatch` failure. - Exclude `hasNonFinalField` from item identity matching; it is enforced via requirements instead of forcing new IDs. - Bump `AnalysisDriver.DATA_VERSION` to 541 for the format change. Why - Consumers that depend on mutability of instance fields (directly or through inheritance) now get targeted invalidation without unnecessary ID churn, improving both correctness and incremental performance. Implementation notes - LibraryManifestBuilder copies `element.hasNonFinalField` into item instances. - Manifest read/write gains a boolean field on `InterfaceItem` (and subclasses) and helpers to encode/decode optional booleans in the requirements stream. - Result printer includes `hasNonFinalField` in interface requirement dumps. Change-Id: Ib132dca582f77df87f995920dd9b73784a4eeefd Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/448444 Reviewed-by: Johnni Winther <johnniwinther@google.com> 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.