[CFE/VM] Fix expression evaluation to not introduce new parameters because of extension types To support expression evaluation on extension types - which are a static thing and thus doesn't exist in the VM - on the CFE side we try to find the available variables so that, for any variables that are found to be extension types, we can treat them as such. This was introduced in https://dart-review.googlesource.com/c/sdk/+/339900. The problem is that this could accidentally _introduce_ new variables, which would introduce new arguments to the created procedure causing weird behavior in the VM as for instance seen in https://github.com/dart-lang/sdk/issues/56911. This CL makes sure to only set the type for already known variables (as passed by the VM), thus not introducing new variables and fixing the issues seen. Fixes https://github.com/dart-lang/sdk/issues/56911 Change-Id: Ie8b8ae12438338e9c3d248d00cc5da81df5b8ece Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/400120 Reviewed-by: Johnni Winther <johnniwinther@google.com> Reviewed-by: Derek Xu <derekx@google.com> Commit-Queue: Jens Johansen <jensj@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.