| commit | 3b39c2637b48f2029543e62758940de80e3e0b61 | [log] [tgz] |
|---|---|---|
| author | Srujan Gaddam <srujzs@google.com> | Thu Aug 21 15:25:57 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 21 15:25:57 2025 -0700 |
| tree | 18dfad5b3fd7c17006a8742c0b506b32e48a4379 | |
| parent | 4ccfbc66ce2b829a41300702ea3c8025cc5dcea8 [diff] |
[ddc] Separate _emitObjectLiteral out from _emitArgumentList Currently _emitArgumentList handles arguments for Dart members, JS interop members, and object literal constructors. It requires an Arguments node, which we end up synthesizing, which messes with parent pointers erroneously. We also have to separate out the arguments and do additional checks later to detect whether the arguments passed correspond to an object literal constructor. Instead, we should create the resulting expression directly in a helper method. A map is passed so that the names of arguments can be easily changed when we handle @JS renaming on object literal constructors. Lastly, we need to avoid wrapping the values with assertInterop in the case where the constructor is from a dart:js_interop interface. That library only statically allows Functions to be passed if they're externalized, in which case we shouldn't tell users to wrap the Function with allowInterop (which doesn't exist anyways in dart:js_interop). Change-Id: If6fdc706e80837ab2b698cca704ffd9f08aed28a Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/446184 Reviewed-by: Nicholas Shahan <nshahan@google.com> Commit-Queue: Srujan Gaddam <srujzs@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.