SyntheticAccessorLowering was initially implemented under the assumption that any access to an invisible declaration will cause an accessor to be generated _in the same file_. Moreover, it's declared in the group of phases that are performed by file. But this assumption is incorrect for constructors which need to be hidden (those which take parameters of inline class types), since such constructor is public and can be called from anywhere. In this case, SyntheticAccessorLowering actually generated a new accessor for the hidden constructor for each (!) source file where that constructor is called, which led to ClassFormatError because of the class file having multiple methods with the same signature. The internal `functionMap` cache didn't help because it's not shared among phase instances for different files (well, it helped to generate not more than one accessor per usage-file). In this change, we use the global cache, stored in JvmBackendContext, for accessors to hidden constructors. Note that after this change, calls to hidden constructors are always transformed to the corresponding accessor in SyntheticAccessorLowering right away, but that accessor might be orphaned for a while (not declared in any parent's declarations). Only when SyntheticAccessorLowering encounters the original constructor which needs to be hidden, it adds the accessor beside it. The test is sensitive to the file order, so both variants are added.
Kotlin Programming Language
Welcome to Kotlin! Some handy links:
- Kotlin Site
- Getting Started Guide
- Try Kotlin
- Kotlin Standard Library
- Issue Tracker
- Forum
- Kotlin Blog
- Follow Kotlin on Twitter
- Public Slack channel
- TeamCity CI build
Editing Kotlin
Build environment requirements
In order to build Kotlin distribution you need to have:
-
JDK 1.6, 1.7, 1.8 and 9
-
Setup environment variables as following:
JAVA_HOME="path to JDK 1.8" JDK_16="path to JDK 1.6" JDK_17="path to JDK 1.7" JDK_18="path to JDK 1.8" JDK_9="path to JDK 9"
For local development, if you're not working on bytecode generation or the standard library, it's OK to have only JDK 1.8 and JDK 9 installed, and to point JDK_16 and JDK_17 environment variables to your JDK 1.8 installation.
You also can use Gradle properties to setup JDK_* variables.
Note: The JDK 6 for MacOS is not available on Oracle's site. You can download it here.
On Windows you might need to add long paths setting to the repo:
git config core.longpaths true
Building
The project is built with Gradle. Run Gradle to build the project and to run the tests using the following command on Unix/macOS:
./gradlew <tasks-and-options>
or the following command on Windows:
gradlew <tasks-and-options>
On the first project configuration gradle will download and setup the dependencies on
intellij-coreis a part of command line compiler and contains only necessary APIs.idea-fullis a full blown IntelliJ IDEA Community Edition to be used in the plugin module.
These dependencies are quite large, so depending on the quality of your internet connection you might face timeouts getting them. In this case you can increase timeout by specifying the following command line parameters on the first run:
./gradlew -Dhttp.socketTimeout=60000 -Dhttp.connectionTimeout=60000
Important gradle tasks
clean- clean build resultsdist- assembles the compiler distribution intodist/kotlinc/folderideaPlugin- assembles the Kotlin IDEA plugin distribution intodist/artifacts/Kotlinfolderinstall- build and install all public artifacts into local maven repositoryrunIde- build IDEA plugin and run IDEA with itcoreLibsTest- build and run stdlib, reflect and kotlin-test testsgradlePluginTest- build and run gradle plugin testscompilerTest- build and run all compiler testsideaPluginTest- build and run all IDEA plugin tests
OPTIONAL: Some artifacts, mainly Maven plugin ones, are built separately with Maven. Refer to libraries/ReadMe.md for details.
Building for different versions of IntelliJ IDEA and Android Studio
Kotlin plugin is intended to work with several recent versions of IntelliJ IDEA and Android Studio. Each platform is allowed to have a different set of features and might provide a slightly different API. Instead of using several parallel Git branches, project stores everything in a single branch, but files may have counterparts with version extensions (*.as32, *.172, *.181). The primary file is expected to be replaced with its counterpart when targeting non-default platform.
More detailed description of this scheme can be found at https://github.com/JetBrains/bunches/blob/master/ReadMe.md.
Usually, there's no need to care about multiple platforms as all features are enabled everywhere by default. Additional counterparts should be created if there's an expected difference in behavior or an incompatible API usage is required and there's no reasonable workaround to save source compatibility. Kotlin plugin contains a pre-commit check that shows a warning if a file has been updated without its counterparts.
Development for some particular platform is possible after 'switching' that can be done with Bunch Tool from the command line.
cd kotlin-project-dir
# switching to IntelliJ Idea 2019.1
bunch switch 191
Working with the project in IntelliJ IDEA
Working with the Kotlin project requires at least IntelliJ IDEA 2019.1. You can download IntelliJ IDEA 2019.1 here.
After cloning the project, to import the project in Intellij choose the project directory in the Open project dialog. Then, after project opened, Select
File -> New... -> Module from Existing Sources in the menu, and select build.gradle.kts file in the project's root folder.
In the import dialog, select use default gradle wrapper.
To be able to run tests from IntelliJ easily, check Delegate IDE build/run actions to Gradle and choose Gradle Test Runner in the Gradle runner settings after importing the project.
At this time, you can use the latest released 1.3.x version of the Kotlin plugin for working with the code. To make sure you have the latest version installed, use Tools | Kotlin | Configure Kotlin Plugin Updates and press "Check for updates now".
Compiling and running
From this root project there are Run/Debug Configurations for running IDEA or the Compiler Tests for example; so if you want to try out the latest and greatest IDEA plugin
- VCS -> Git -> Pull
- Run the "IDEA" run configuration in the project
- a child IntelliJ IDEA with the Kotlin plugin will then startup
Including into composite build
To include kotlin compiler into composite build you need to define dependencySubstitution for kotlin-compiler module in settings.gradle
includeBuild('/path/to/kotlin') {
dependencySubstitution {
substitute module('org.jetbrains.kotlin:kotlin-compiler') with project(':include:kotlin-compiler')
}
}
License
Kotlin is distributed under the terms of the Apache License (Version 2.0). See license folder for details.
Contributing
Please be sure to review Kotlin's contributing guidelines to learn how to help the project.