[vm] Take advantage of FunctionInvocation.kind to detect non-dynamic closure calls The Incremental Kernel Compiler (IKG) will produce kernel files without metadata. Right now the VM will make all closure calls dynamic calls if the call-site attribute metadata is not present. This causes closure code to run significantly slower due to dyn:call forwarders and the type checks it will perform. This change takes - in addition to the metadata - the new FunctionInvocation.kind into account - which also tells us whether a function invocation is based on a real function type. Fixes https://github.com/dart-lang/sdk/issues/46320 Fixes https://github.com/dart-lang/sdk/issues/45421 TEST=vm/cc/StreamingFlowGraphBuilder_TypedClosureCall Change-Id: Ie1136c3727fc8b5e3e3b9822a1db9479fa9da689 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/203302 Commit-Queue: Martin Kustermann <kustermann@google.com> Reviewed-by: Alexander Markov <alexmarkov@google.com> Reviewed-by: Slava Egorov <vegorov@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
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 on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.