commit | f4b41f09028e3e77a801e1262c36bcf11ec1eb4c | [log] [tgz] |
---|---|---|
author | Ömer Ağacan <omersa@google.com> | Tue Mar 18 04:11:41 2025 -0700 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 18 04:11:41 2025 -0700 |
tree | fd1d3c717a43a5d635d4b76ec73ddb10f17bde58 | |
parent | 367474d5767ad4fc22db8f0f5c51f71c7350b9ab [diff] |
[dart2wasm] Fix handling of --define/-D When parsing `--define` or `-D` arguments don't split the the value by commas. This is consistent with how dart2js handles `-D`, but inconsistent with how VM handles it. Example: void main() { print(const String.fromEnvironment("FOO")); } When compiled with `dart compile js -DFOO="a, b"` and run, dart2js prints a, b VM prints (when compiled to exe) a Between these two, I think dart2js' behavior is more common, so we follow dart2js. Also update compile_benchmark to avoid splitting a single argument "a b" into "a" and "b" when parsing the arguments and then splicing them back before calling `dart2wasm`. Also update the test runner and ddc batch mode argument parser to handle splitting quoted arguments in `// dart2jsOption = ...` and the same options for ddc and dart2wasm, by moving dart2js's `splitLine` to a new library and reusing it in the test runner and ddc. Fixes https://github.com/flutter/flutter/issues/164873. See also https://github.com/dart-lang/sdk/issues/60341 for relevant future work. Change-Id: Idbdf69072fa212c8e4a390990577eb5a57b49e8a Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/415280 Reviewed-by: Martin Kustermann <kustermann@google.com> Commit-Queue: Ömer Ağacan <omersa@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.