Samir Jindel
6c5d1fba95
Summary: Previously, there was no support for generic methods in kernel. This prevented us from being able to pass captured type arguments to the target top-level function in converted closures, so these type arguments were always instantiated to 'dynamic'. Now, we save the type arguments to the closure creation operation in the context, and read them out and forward them appropriately in closure wrapper function. Since fasta doesn't currently support generic methods (their type parameters are replaced by 'dynamic'), only top-level generic functions can surface in kernel, as they are generated by closure conversion of closures that capture type parameters of a class. My focus here is enabling closure conversion to work in only these cases, and as such, the code has some temporary "hacks" in the VM that may not work for generic member functions or generic closures when they are enabled in fasta. Test Plan: I ran all the tests in closures/, and those which were previously expected to crash due to missing VM support now pass and produce correct results. Further testing is paused until we understand why the recent commit "[kernel] Insert kernel bodies into VM heap" has broken all these tests. Reviewers: regis@google.com, jensj@google.com, dmitryas@google.com BUG= R=dmitryas@google.com, jensj@google.com Review-Url: https://codereview.chromium.org/2998803002 .
Dart Kernel
Dart Kernel is a small high-level language derived from Dart. It is designed for use as an intermediate format for whole-program analysis and transformations, and as a frontend for codegen and execution backends.
The kernel language has in-memory representations in Dart and C++, and can be serialized as binary or text.
Both the kernel language and its implementations are unstable and are under development.
This package contains the Dart part of the implementation and contains:
- A transformable IR for the kernel language
- A frontend based on the analyzer
- Serialization of kernel code
Note: The APIs in this package are in an early state; developers should be careful about depending on this package.
Getting Kernel
Checkout the repository and run pub get:
git clone https://github.com/dart-lang/kernel
cd kernel
pub get
Command-Line Tool
Run tool/dartk.dart from the command-line to convert between .dart files
and the serialized binary and textual formats.
dartk expects the .dill extension for files in the binary format.
The textual format has no preferred extension right now.
Example commands:
dartk foo.dart # print text IR for foo.dart
dartk foo.dart -ofoo.dill # write binary IR for foo.dart to foo.dill
dartk foo.dill # print text IR for binary file foo.dill
Pass the --link or -l flag to link all transitive dependencies into one file:
dartk myapp.dart -ppackages -l -omyapp.dill # Bundle everything.
dartk myapp.dill # Print it back out in a (very, very long) textual format.
See ast.dart for the in-memory IR, or binary.md for a description of the binary format. For now, the textual format is very ad-hoc and cannot be parsed back in.
Testing
If you plan to make changes to kernel, get a checkout of the Dartk SDK and run:
tool/regenerate_dill_files.dart --sdk <path to SDK checkout>
pub run test
Linking
Linking from binary files is not yet implemented. In order to compile a whole program, currently everything must be compiled from source at once.