| commit | 6b10c3899e34c85b0d2e560dcda62876d3559834 | [log] [tgz] |
|---|---|---|
| author | Kallen Tu <kallentu@google.com> | Wed Feb 19 07:20:51 2025 -0800 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Feb 19 07:20:51 2025 -0800 |
| tree | 47eedb8c7248e3220d8ca405fd97284b9166042a | |
| parent | 163c9a371fc4c7512fa78d9f4e9b3cc6bdca12d0 [diff] |
[stable][cfe] Issue 60121: Fix bug with isWildcard flag for formals. Issue description: Users are finding that their debug variables are evaluated to the wrong values and it's due to wildcard variables being included, but being unable to be evaluated. Wildcard variables shouldn't be able to be evaluated in the first place. What is the fix: Correctly propagate the `isWildcard` flag in the CFE to formal parameters. The VM uses this flag to determine if the variable can be excluded from debugging evaluation. The flag is now set correctly with the fix and won't appear in VM debug. Why cherry-pick: This is causing debug variables to be evaluated incorrectly because wildcard variables are appearing in the debug panel of variables and shouldn't be. Risk: Low, fixes wildcard variables that are formal parameters and touches no other code. This is code that should've been in the feature from the start. Issue link(s): https://github.com/dart-lang/sdk/issues/60121 Cherry-pick: https://dart-review.googlesource.com/c/sdk/+/410161 Change-Id: Ie7aa3561183e6e326d65c09165a132d6bb3e72a2 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/410640 Reviewed-by: Johnni Winther <johnniwinther@google.com> Reviewed-by: Siva Annamalai <asiva@google.com> Commit-Queue: Kevin Chisholm <kevinjchisholm@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.