| commit | baa7da33fe34addc2fc30e1594f56da4077e7994 | [log] [tgz] |
|---|---|---|
| author | Konstantin Shcheglov <scheglov@google.com> | Mon Sep 01 10:33:42 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Sep 01 10:33:42 2025 -0700 |
| tree | d3605e1143ba8a7021d3bb7857d697cb6efa5531 | |
| parent | 51b7329edf3cca56b833706d7b97baca9a159b54 [diff] |
Elements. Fix method top-merge reuse and default constructor flag Correct two issues in element handling: * In `InheritanceManager3._topMerge`, when merging methods, check for an existing `MethodElementImpl` at `@method/<name>` (not a setter). If present, reuse it; otherwise assert the slot is empty before synthesizing. Similar assertions are added to getter/setter paths to guard against accidental reuse of a wrong-kind element. * In `SubstitutedConstructorElementImpl`, fix `isDefaultConstructor` to forward to `baseElement.isDefaultConstructor` (it previously forwarded to `isConst`). These changes prevent creating fresh synthetic methods when a correct method already exists, preserving element identity and avoiding wrong-kind lookups. The constructor fix restores accurate default constructor detection, which can affect downstream diagnostics and presentation. Additional tests cover method top-merge in both “existing” and “synthetic” scenarios, aligning method coverage with existing getter/setter cases. Change-Id: I09c3aaa7cb89f216d6d3101bbad835567df5b213 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/447961 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.