Based on the documentation, no-arg compiler plugin is expected to generate synthetic constructors, but in practice they are non-synthetic (on purpose I think, like the default constructor generated when optional parameters have all their default values specified). But isn't the documentation misleading ? https://kotlinlang.org/docs/reference/compiler-plugins.html

hey @here is there documentation about custom compiler plugins?

Hey folks. Anyone stumbled upon build cache being ignored when compiling with

kotlin.compiler.execution.strategy=in-process

?

@thalescm Actually, these 4 stages are: 1) stub generation 2) annotation processing 3) kt compilation 4) java compilation. There is some documentation available in our website: https://kotlinlang.org/docs/reference/kapt.html#using-in-cli.

--debug

is definitely a bit noisy. I think you can run with the

--info

option instead, it should also print all options passed to kotlinc. As about incremental compilation, I think @alexey.tsvetkov can help you much better than me.

is that right?

Another question is that, when I try to run

kotlinc

the first time (to generate stubs) it already fail cause it’s looking for expected generated classes that are used the sources, so, what should I pass as sources when generating stubs and running apt?

Meanwhile I tried to find the documentation of the kotlin compiler, to figure out which compiler options are available, but unfortunately I could not find it. Does someone have a link?

Great, thank you! I didn't think of starting from diagnostics and go up from there, that's a useful method.

I have a Java method with the signature

void awesomeMethod(Class<? extends Parent> klasss)

but the compiler (in Android Studio) doesn’t accept an instance Kotlin class

class Child : Parent

as a valid parameter value.

Hi all. I've got a bit of a silly question for you. In the grammar,

atomicExpression

includes a number of things that can be evaluated, like

literalConstant

and

functionLiteral

. Even the different

jump

structures (like

throw

and

return

) appear to technically evaluate to

Nothing

. But the list also includes

loop

, which doesn't appear to be an expression. In fact, if you try to assign a

for

loop to a variable, the compiler says that "For is not an expression, and only expressions are allowed here." So, I was wondering, why does

loop

show up as part of

atomicExpression

in the grammar? Is there some context in which loops can be evaluated?

Full stacktrace:

Error:Kotlin: [Internal Error] java.lang.IllegalStateException: The provided plugin org.jetbrains.kotlin.kapt3.Kapt3ComponentRegistrar is not compatible with this version of compiler
	at org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreEnvironment.<init>(KotlinCoreEnvironment.kt:198)
	at org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreEnvironment.<init>(KotlinCoreEnvironment.kt:117)
	at org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreEnvironment$Companion.createForProduction(KotlinCoreEnvironment.kt:446)
	at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.createCoreEnvironment(K2JVMCompiler.kt:295)
	at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:147)
	at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:51)
	at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.java:94)
	at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.java:50)
	at org.jetbrains.kotlin.cli.common.CLITool.exec(CLITool.kt:88)
	at org.jetbrains.kotlin.daemon.CompileServiceImpl$compile$$inlined$ifAlive$lambda$1.invoke(CompileServiceImpl.kt:402)
	at org.jetbrains.kotlin.daemon.CompileServiceImpl$compile$$inlined$ifAlive$lambda$1.invoke(CompileServiceImpl.kt:101)
	at org.jetbrains.kotlin.daemon.CompileServiceImpl$doCompile$$inlined$ifAlive$lambda$2.invoke(CompileServiceImpl.kt:929)
	at org.jetbrains.kotlin.daemon.CompileServiceImpl$doCompile$$inlined$ifAlive$lambda$2.invoke(CompileServiceImpl.kt:101)
	at org.jetbrains.kotlin.daemon.common.DummyProfiler.withMeasure(PerfUtils.kt:137)
	at org.jetbrains.kotlin.daemon.CompileServiceImpl.checkedCompile(CompileServiceImpl.kt:969)
	at org.jetbrains.kotlin.daemon.CompileServiceImpl.doCompile(CompileServiceImpl.kt:928)
	at org.jetbrains.kotlin.daemon.CompileServiceImpl.compile(CompileServiceImpl.kt:400)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:564)
	at java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359)
	at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200)
	at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197)
	at java.base/java.security.AccessController.doPrivileged(Native Method)
	at java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196)
	at java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562)
	at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796)
	at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677)
	at java.base/java.security.AccessController.doPrivileged(Native Method)
	at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:676)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:844)
Caused by: java.lang.AbstractMethodError
	at org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreEnvironment.<init>(KotlinCoreEnvironment.kt:190)
	... 33 more

Would it be possible to change the flags of generated multifile class parts so they have

Elements.Origin.MANDATED

or

EXPLICIT

like the generated synthetic methods with

$annotations

suffix? That would make it possible to process annotations on top-level properties and type aliases in files with

@JvmMultifileClass

annotation. In order to process annotations on properties or type aliases you need to get ahold of the

propertyName$annotations()V

method but for multifile class parts this element is in the synthetic

FacadeNameKt__FileNameKt

class. Since the class is synthetic it is never loaded by the annotation processor and can not be accessed, even if you know the name from parsing the facade class'

@Metadata

annotation

hey everyone, just wanted to drop a link here and maybe pique some peoples interest. Its a Kotlin Language Server that I've been contributing to bit by bit, unfortunately myself and the main maintainer are currently bogged down by our studies, we'd be delighted if people wanted to help out and contribute, iron out the bugs and get the issues list down :) https://github.com/fwcd/KotlinLanguageServer

Is there any performance benefit (or even penalty) in making all classes of an application (not library)

internal

? Like in Swift where when everything is internal and thus never used from other modules it can be optimized and inlined quite a lot.

Hello, i’m trying to make a compiler plugin for kotlin native that generates

Deferred

return type methods for

suspend

functions e.g.

suspend fun foo(): String = "Hello world!"

would generate an additional method

fun foo(scope: CoroutineScope): Deferred<String> = scope.async { "Hello world!" }

As i try to hook into ir codegen i’m getting this exception:

exception: java.lang.IllegalStateException: The provided plugin com.nfq.NativeSuspendRegistrar is not compatible with this version of compiler
        at org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreEnvironment.<init>(KotlinCoreEnvironment.kt:203)
        at org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreEnvironment.<init>(KotlinCoreEnvironment.kt:121)
        at org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreEnvironment$Companion.createForProduction(KotlinCoreEnvironment.kt:513)
        at org.jetbrains.kotlin.cli.bc.K2Native.doExecute(K2Native.kt:57)
        at org.jetbrains.kotlin.cli.bc.K2Native.doExecute(K2Native.kt:35)
        at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.java:96)
        at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.java:52)
        at org.jetbrains.kotlin.cli.common.CLITool.exec(CLITool.kt:93)
        at org.jetbrains.kotlin.cli.common.CLITool.exec(CLITool.kt:71)
        at org.jetbrains.kotlin.cli.common.CLITool.exec(CLITool.kt:39)
        at org.jetbrains.kotlin.cli.common.CLITool$Companion.doMainNoExit(CLITool.kt:202)
        at org.jetbrains.kotlin.cli.common.CLITool$Companion.doMain(CLITool.kt:194)
        at org.jetbrains.kotlin.cli.bc.K2Native$Companion$main$1.invoke(K2Native.kt:214)
        at org.jetbrains.kotlin.cli.bc.K2Native$Companion$main$1.invoke(K2Native.kt:205)
        at org.jetbrains.kotlin.konan.util.UtilKt.profileIf(Util.kt:37)
        at org.jetbrains.kotlin.konan.util.UtilKt.profile(Util.kt:31)
        at org.jetbrains.kotlin.cli.bc.K2Native$Companion.main(K2Native.kt:207)
        at org.jetbrains.kotlin.cli.bc.K2NativeKt.main(K2Native.kt:259)
        at org.jetbrains.kotlin.cli.utilities.MainKt.main(main.kt:16)
Caused by: java.lang.AbstractMethodError
        at org.jetbrains.kotlin.cli.jvm.compiler.KotlinCoreEnvironment.<init>(KotlinCoreEnvironment.kt:195)
        ... 18 more

My build.gradle looks like this:

apply plugin: 'org.jetbrains.kotlin.jvm'
apply plugin: 'kotlin-kapt'

repositories {
    jcenter()
}

dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib:$kotlinVersion"
    implementation "org.jetbrains.kotlin:kotlin-compiler-embeddable:$kotlinVersion"

    compileOnly 'com.google.auto.service:auto-service:1.0-rc4'
    kapt 'com.google.auto.service:auto-service:1.0-rc4'
}

And my ComponenRegistrar looks like this:

@AutoService(ComponentRegistrar::class)
class NativeSuspendRegistrar : ComponentRegistrar {

    override fun registerProjectComponents(project: MockProject, configuration: CompilerConfiguration) {
        IrGenerationExtension.registerExtension(project, NativeSuspendIrGenerationExtension())
    }
}

I use Kotlin 1.3.11

You can use the bytecode inspector to view it exactly

Hello. Today I learned that

@JvmStatic

really makes a method static inside an object declaration, if possible. So, I can imagine a corner case: 1. Module A contains an

interface A {}

2. Module B implements it:

object B : A {
    @JvmStatic fun doSomething()
}

3. Module A adds a method in next version:

interface A { fun doSomething() }

Expected:

B.doSomething()

and

(B as A).doSomething()

is the same method. But I think AbstractMethodError will occur instead.

Does anyone here know in which circumstances a package or module element gets a

@kotlin.Metadata

annotation?

Doesn't

Metadata

note which primary constructor parameters are also properties?

/**
         * Signifies that the corresponding property has a getter.
         */
        @JvmField
        val HAS_GETTER = Flag(F.HAS_GETTER)

And can there be properties without a getter? 🤔 Even with

@JvmField

the flag

HAS_GETTER

is set.

Property annotations create a

property$annotations

method. The method is still there at runtime even if all properties have

SOURCE

retention and thus no annotations are left in the binary or at runtime. Maybe the synthetic method can be deleted safely at some point?

If I am getting a

java.lang.VerifyError: Bad local variable type

does that mean I found a compiler bug? I have a

private suspend inline fun

and when I remove the

inline

part it seems happy…

/**
 * Signifies that the corresponding property has a getter.
 */
@JvmField
val HAS_GETTER = Flag(F.HAS_GETTER)

Can there ever be a property without a getter in the Kotlin metadata?

What is the benefit of having local delegated properties listed in

@Metadata

?

And can only a file facade class contain type aliases?

And a quirk in

@Metadata

with properties:

var test = ""
	get
	private set

Both, getter and setter, are reported as

Flag.IS_NOT_DEFAULT

in this case but clearly have default and no custom implementation. Bug? 🤔

And another one in `@Metadata`:

// at file-level
var x = 2

property has flag

HAS_SETTER

set property doesn't contain a setter parameter 🤔

I’ve created a compiler plugin to enable Spek (https://github.com/spekframework/spek) to be used with Kotlin/Native. The compiler plugin performs a similar role to what the kotlin-test stuff in the compiler does - it looks for tests and registers them so that reflection at runtime is not necessary. However, I’ve never written a compiler plugin before and while it works, I don’t know if that’s because it should work or if it’s just a happy coincidence 🙂 Is there anyone here who knows what they’re doing who could have a look at it and tell me if I’m doing anything crazy? https://github.com/charleskorn/spek/blob/compiler-plugin/spek-kotlin-compiler-plugin/src/main/kotlin/org/spekframework/spek2/kotlincompilerplugin/SpekExtension.kt is the meaty part

I'm getting a backend internal error trying to compile the following code:

enum class Enum
@JvmOverloads
constructor(a: O = O(), b: P = P()) {
}

Is this a known problem?