commit | bb0580f5a5461bbabc2b17ea0399aa450f75ad3b | [log] [tgz] |
---|---|---|
author | Konstantin Shcheglov <scheglov@google.com> | Tue Aug 19 11:28:39 2025 -0700 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 19 11:28:39 2025 -0700 |
tree | 07cfbbfd0f17fabe39d78b13987be00083e6dd9e | |
parent | 37ac8e4b4c3f93a2aabacf5341fd81a67f67846b [diff] |
Elements. Unify interface-cycle handling for extension types Unifies extension type cycle breaking with the existing `breakInterfaceCycles()` flow used for other elements and removes the bespoke walker in `summary2/extension_type.dart`. This consolidates the logic and ensures consistent behavior across element kinds. Key changes: - Move `hasImplementsSelfReference` and `hasRepresentationSelfReference` from fragments to `ExtensionTypeElementImpl`. Flags are now owned and serialized by the element. - Update summary I/O: writer emits and reader consumes the flags at the element level; fragment-level reads/writes are removed. - Adjust `ErrorVerifier` to read flags via `fragment.element`. - Handle extension types inside `interface_cycles.dart`: on an SCC, mark `hasImplementsSelfReference` and replace `interfaces` with `Object` or `Object?` depending on the representation’s nullability. - Bump `DATA_VERSION` to 524 due to summary layout changes. Why: - Eliminates duplicate, divergent cycle-breaking logic for extension types. - Clarifies ownership of self-reference state and simplifies serialization. - Produces consistent diagnostics and interface normalization across element kinds. Impact: - Requires a format bump; older summaries are invalidated as intended. - Fragment-level self-reference bits are removed in favor of element-level flags. Change-Id: Ifabb0acb2ce60353bbfe10ee5877c0c66cee5202 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/445961 Commit-Queue: Konstantin Shcheglov <scheglov@google.com> Reviewed-by: Paul Berry <paulberry@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.