[vm,aot] Use inferred type arguments to remove type checks When TFA is able to infer type arguments, write _exact type_ into the inferred types metadata. Use inferred exact type in the VM: load it from metadata and attach to a field if necessary. CompileType is extended to hold exact type if it is known. In the instruction canonicalizer, if type arguments are loaded from a value which has a known exact type, then replace this LoadField with Constant type arguments from exact type. This allows VM to use inferred type arguments to remove parameter type checks. TEST=runtime/tests/vm/dart/eliminate_type_check_using_exact_type_il_test.dart Closes https://github.com/dart-lang/sdk/issues/61083 Change-Id: I766c5e8c49be406f3e12d38e8d966e5813500c4d Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/440064 Commit-Queue: Alexander Markov <alexmarkov@google.com> Reviewed-by: Slava Egorov <vegorov@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.