commit | ba90daf304abb446be20816709adee709d7b1021 | [log] [tgz] |
---|---|---|
author | MarkZ <markzipan@google.com> | Mon Mar 17 10:34:48 2025 -0700 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 17 10:34:48 2025 -0700 |
tree | 7d01a1f7179a6300b1e9c0b3574f4ba6cfa18ad6 | |
parent | fd3eaa68318850697eb610483b8f8f866c28cdc6 [diff] |
Reland "[ddc] Overhauling tearoff equality and identity." This new update adds fixes + tests for cross-module super mixins. Super getters can refer to mixins compiled in other modules, so we need to expose all mixin names to make them accessible from their enclosing library. This is a reland of commit e4c4d0f839ce4998a46ac3997aea2668d3edd48f Original change's description: > [ddc] Overhauling tearoff equality and identity. > > Hot reload requires DDC to update how its tearoffs are represented. Tearoffs obey the following conventions: > * Instance tearoffs are never identical > * Tearoffs with the same object target and name have the same hash code (even if they resolve to different functions across hot reloads) > * Two separate tearoffs of the same member are equal > > To support this, tearoff equality must not depend on the bound object and method but a composite of the bound object, torn off member name, and the exact class/object from which the member was torn off. > > Notable changes: > * Methods' immediately bound targets are emitted with member signatures. This is required to determine the bound targets for instance and dynamic tearoffs. Bound targets are identified by `libraryUri:class` strings. > * `applyMixin` passes in a 'true' bound target. This is because mixin applications' members are considered children of their 'on' class (not the mixed in class) wrt equality/hashCode. > * `bind` is modified to pass in its 'true' bound object to support mixins' super getters. > * `tearoff` and `staticTearoff` are modified to accept a bound target string (only required for static tearoffs, as they are bound at tearoff-creation-time). > * Static tearoffs avoid using their bound object for hashcode and equality, as these libraries may be wrapped in proxy objects. > * Tearoff equality and hashCode are updated to consider bound object, bound name, and its bound method's immediate target. > * 'noSuchMethod' and 'toString' methods are always accessed through their extension property during signature lookups. > > > Change-Id: Ica5501b6860c605db50aa945bafb6802a7317511 > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/406723 > Reviewed-by: Nate Biggs <natebiggs@google.com> > Reviewed-by: Nicholas Shahan <nshahan@google.com> > Commit-Queue: Mark Zhou <markzipan@google.com> Change-Id: I645992030f9106c158426412387ddecafc78e3f4 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/415102 Reviewed-by: Nate Biggs <natebiggs@google.com> Commit-Queue: Mark Zhou <markzipan@google.com> Reviewed-by: Nicholas Shahan <nshahan@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.