[dart2wasm] Synthesize null when calling JS functions without result, Remove inlining in js interop transformer When we call out to JS and the function type is declared as `void` we don't observe the result from JS. That means we can import the JS function as a wasm function type without results. We then synthesize a `null` value, in case a caller of the external JS function uses/observes the `void` result value. => This CL does the same for `JS<void>(...)` calls. We also remove the "inline" replacement optimization in the js interop transformer. That makes all `JS<...>()` calls to be handled in a uniform way. => Our backend's inliner should inline it iff beneficial for size. Change-Id: I78032aae0dcdcaaf52701c628cea71af1de0d5e6 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/499880 Commit-Queue: Martin Kustermann <kustermann@google.com> Reviewed-by: 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.