Alexander Udalov
6d16ea0a3a
The main problem here is that moduleName that is being passed to KPackageImpl is useless: as can be seen in ClosureCodegen.generateCallableReferenceDeclarationContainer, the name of the current module is always written to the class file for a callable reference, not the name of the module of the referenced declaration. This resulted in reflection not loading the correct .kotlin_module file and subsequently not finding the required file facade for a top-level function. The commit does not fix the issue with the incorrect module name written in the back-end, but workarounds it. It turns out, reflection can figure out the name of the module of the referenced declaration itself by parsing the header from the given java.lang.Class object for a single-file/multi-file package facade and extract the package_module_name protobuf extension. Similar code was already there in Member.getKPackage() in ReflectJvmMapping.kt but it did not support multi-file classes, of which there are a lot in the standard library; this is now supported #KT-12630 Fixed #KT-14731 Fixed
JavaScript Translation
This module performs the translation of Kotlin source code to JavaScript.
There are various Kotlin APIs to JavaScript environments and libraries in the js.libraries project.
Compiling the standard Kotlin library to JavaScript
- the kotlin-js-library module creates a jar containing all the Kotlin source code for the runtime and standard kotlin library code (both definitions and implementation code) to be compiled to JavaScript.
- the kotlin-js-tests module then compiles a selection of test cases from the Kotlin standard library for the JVM to JavaScript. These tests can then be run in a web browser using QUnit
- the kotlin-js-tests-junit then runs the JavaScript tests for the standard library inside JUnit using Selenium and the underlying JavaScript & QUnit so that the JavaScript can be tested as part of the maven continuous integration build.
Reusing JVM based test cases in JavaScript
Any Kotlin test cases using the org.junit.Test annotation and the kotlin.test package, such as this test case are automatically converted to JavaScript using QUnit.
This allows the test cases to be ran directly in a web page in any web browser.
Using the Kotlin Library in JavaScript
There is a simple sample which shows how to use the Kotlin Standard Library from inside JavaScript in a web page or in a JVM using kool.io's JavaFX browser
Contributing
We love contributions! The JavaScript translation could really use your help! If you fancy contributing:
- check the contributing section on general stuff like getting the code etc
- here's the list of current excluded standard library unit tests from the JavaScript JUnit test run; see if you can fix one of those? (Check the TODO commands and the links to specific issues)
- try fix one of the pending JavaScript translation issues