hm, after ~4 hours of trying I've downloaded the file via Chrome

Anybody! I am (still) compiling the stdlib from sources, and I get

Incompatible classes were found in dependencies. Remove them from the classpath or use '-Xskip-metadata-version-check' to suppress errors
[ERROR] /Users/voddan/Programming/kotlin/libraries/stdlib/src/generated/_Arrays.kt: (1, 7) Class 'kotlin.jvm.JvmMultifileClass' is compiled by a pre-release version of Kotlin and cannot be loaded by this version of the compiler

What is the recommended way to deal with it?

Hello. If I just updated kotlin source code from github but it fails to build, is there a teamcity to check that the build is broken (and it’s not my local problem)?

So I'm mimicking what they did for painless but without having to write a whole new scripting language to do it, and it would be a better version because Kotlin is more expressive when doing things like long functional chains that painless just fails at

📣 A note to contributors working within the

libraries

directory: now you need to run gradle build step before running maven. More details in the readme: https://github.com/JetBrains/kotlin/blob/master/libraries/ReadMe.md And if you work solely on the standard library, it's enough to run just gradle build.

not sure if this is a viable solution. I'm working on https://youtrack.jetbrains.com/issue/KT-17660. I'm adding an inspection and as a quickfix I want to reuse the intention "Add names to call arguments" without it appearing twice in the Alt + Enter menu.

@yole can you review https://github.com/JetBrains/kotlin/pull/1011 again when you have time? thx

kotlin-test documentation seems to be broken https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.test/

especially with

INDICES

message has been deleted

@yole Could you elaborate on your comment on this issue when you get a chance, please? https://youtrack.jetbrains.com/issue/KT-17743 I'm using IntelliJ 2017.2 EAP and the latest dev plugin it wants me to install is 1.1.4-dev-469, yet I'm getting the crash the issue reports. Is there not a 1.1.4-dev plugin available for 2017.2? Why does the repository recommend this dev version, then? Or are you referring to the need to install a 2017.2 version of the Android plugin? (Which I also don't understand, since it works fine until upgrading the Kotlin plugin to 1.1.4-dev.)

Hi, I am trying to make a change where parentheses are also deleted after deleting the last unused constructor parameter. So basically

class TestTestTest(val param: String)

->

class TestTestTest

instead of

class TestTestTest()

. I have been able to do so by these changes(https://github.com/shubham2892/kotlin/commit/1b8674496721d301819fdbc17ce1eeda27a83775) but I am getting the above error. I am having hardtime understanding how the

runSignature

method call is acquiring the write lock.

there's a general "we need more settings" issue here: https://youtrack.jetbrains.com/issue/KT-9423

has anyone gotten the kotlin tests to run in IDEA vs from ant? i get resolution errors. 😕

What about this one: https://youtrack.jetbrains.com/issue/KT-12597 ? If I understand correctly, basically there is needed to port https://github.com/JetBrains/android/blob/master/android/src/org/jetbrains/android/AndroidGotoRelatedProvider.java to Kotlin repo and it looks like easy enough for grab. I would like work on this, because my team is missing this feature.

@marcinmoskala But bytecode for implicit and explicit default constructors are the same: on bytecode level it's always explicit. Just compare bytecode before decompilation. So decompiler know nothing about original Kotlin code, just decompiles bytecode to source code according his own internal logic.

can a

com.intellij.codeInspection.LocalQuickFix

be disabled? It doesn't seem to have an

isAvilable

function

Are test files automatically generated from testData? If so, how should I generate them after adding a new test?

I don't know if this is the right place, but I want to contribute to Kotlin. Unfortunately I can't build the project. I have the same error as https://kotlinlang.slack.com/archives/C19FD9681/p1499360862769923, but when I use the external gradle and maven in combination with java8, my project still don't build. Can anyone help me?

@voddan if you or anyone else were still wondering, the source for actually parsing

when

is here: https://github.com/JetBrains/kotlin/blob/master/compiler/frontend/src/org/jetbrains/kotlin/parsing/KotlinExpressionParsing.java#L839

Hi! I have a question related to reified parameters. When this code is compiled:

abstract class A<T>

class B : A<Callable<String>>()

Then the correct

@Metadata

annotation is generated on `B`:

@Metadata(
   mv = {1, 1, 6},
   bv = {1, 0, 1},
   k = 1,
   d1 = {"\u0000\u0014\n\u0002\u0018\u0002\n\u0002\u0018\u0002\n\u0002\u0018\u0002\n\u0002\u0010\u000e\n\u0002\b\u0002\u0018\u00002\u000e\u0012\n\u0012\b\u0012\u0004\u0012\u00020\u00030\u00020\u0001B\u0005¢\u0006\u0002\u0010\u0004¨\u0006\u0005"},
   d2 = {"LB;", "LA;", "Ljava/util/concurrent/Callable;", "", "()V", "production sources for module app_main"}
)

(notice the reference to

Ljava/util/concurrent/Callable

) Now when this code is compiled instead:

abstract class A<T>

inline fun <reified T> a() = object : A<T>() {}

val B = a<Callable<String>>()

Then this

@Metadata

annotation is generated on the anonymous class:

@Metadata(
   mv = {1, 1, 6},
   bv = {1, 0, 1},
   k = 1,
   d1 = {"\u0000\r\n\u0000\n\u0002\u0018\u0002\n\u0002\b\u0002*\u0001\u0000\b\n\u0018\u00002\b\u0012\u0004\u0012\u00028\u00000\u0001B\u0005¢\u0006\u0002\u0010\u0002¨\u0006\u0003"},
   d2 = {"TestKt$a$1", "LA;", "()V", "production sources for module app_main"}
)

All type information is completely lost... Is that the intended behaviour? Can this be avoided?

I'm programmatically accessing

kotlinc

and feeding it snippets to verify they can be compiled. Is there a way to also evaluate expressions and obtain their results in the same way the

kotlinc

REPL does? Any help or pointers in the right direction are appreciated 🙂

can i indulge someone in exploring the limits of kotlin polymorphic syntax?

What is the process for improving the documentation? Should I open a KT ticket to document the improvement? Or can I just create the PR and explain the improvement there?

I have a problem with getting getter annotation from property reference. Here is annotation:

class A {
    @get:Arg val a: Int by BoundToValueDelegateProvider()
}

Inside

provideDelegate

I have property reference

operator fun provideDelegate(
        thisRef: Any?,
        prop: KProperty<*>
): ReadWriteProperty<Any, T> {
    val annotation1 = prop.getter.findAnnotation<Arg>() // This is null
    val annotation2 = prop.javaGetter?.getAnnotation(Arg::class.java) // This is null too
    // ...
}

It this bug or expected behavior?

done

http://demo.kama.zone/#/KamaHQ/dummy/554 user: user pass: user 😉