Good enough indication is that you are first to ask for it 🙂

oops sorry.. its just the scripting support is getting to be really good! and we are already trying to package it in our docker build VM

@sss sorry for the late answer, but you can in fact download the zipped release containing all you need for the command line from github: https://github.com/JetBrains/kotlin/releases/tag/v1.1-M03

@ilya.chernikov thanks for this! the problem is that its not discoverable (since you do daily builds as well). If you could just put these links in your regular release pages (https://bintray.com/kotlin/kotlin-eap-1.1/kotlin/1.1-M03) or even the blog post ... that would be awesome

you can read the conversation above... (and in another channel). a lot of people did not know if EAP releases were fully built or released only as jars

Yep, I realised that. Thanks for turning our attention to that topic. We’ll try to do something about it.

KT 1.1-M02; running/making from IDEA it works, but building with gradle (with a kotlin buildscript), i get an exception compiling a program. error:

ERROR: Exception while analyzing expression at (30,37) in /Users/bhaug/Documents/Projects/knaif/src/main/kotlin/net/berndhaug/knaif/Knaif.kt:
String::trim

java.lang.IllegalStateException: @NotNull method org/jetbrains/kotlin/builtins/KotlinBuiltIns.getBuiltInClassByName must not return null
    at org.jetbrains.kotlin.builtins.KotlinBuiltIns.getBuiltInClassByName(KotlinBuiltIns.java:305)
    at org.jetbrains.kotlin.builtins.KotlinBuiltIns.getBuiltInClassByName(KotlinBuiltIns.java:298)
    at org.jetbrains.kotlin.builtins.FunctionTypesKt.getFunctionTypeArgumentProjections(functionTypes.kt:125)
    at org.jetbrains.kotlin.builtins.ReflectionTypes.getKFunctionType(ReflectionTypes.kt:80)

line 30 is

return contents.split("\n").map(String::trim).filter { it != "" }.map(Duration.Companion::fromLine)

do you see anything obvious/known I’m triggering or something that’s known fixed in 1.1-M03? not sure whether I want to upgrade right now because the plugin works well for me right now, but this is kinda showstopper.

@itbeha if you’re using Gradle 3.2, this is a known problem: https://youtrack.jetbrains.com/issue/KT-14798

@udalov ticket says works with 3.1, i’m on 3.1. also the error & lines is different even though the trace has similar symbols.

difference in the exception message is related to the fact that Gradle is being run without

-ea

in your case, I believe

hi, is kotlin 1.1-M03 released on any public repository? gradle cannot find it on any standard repository

@pawel_byszewski https://dl.bintray.com/kotlin/kotlin-eap-1.1/ Check "How to Try It” section here: https://blog.jetbrains.com/kotlin/2016/11/kotlin-1-1-m03-is-here/

I have been using Kotlin since 1.0-M01 and 1.1 for ten minutes and I have some basic question. Is there any chance to use such fancy syntax for coroutines

val future = async<String> {
        (1..5).map {
            await(startLongAsyncOperation(it))
        }.joinToString("\n")
    }

kotlinx.coroutines requires at least 24 Android API level that is obviously unacceptable at this moment

as I see there is some alternative for kotlinx, metalabdesign/AsyncAwait

kotlinx.coroutines is merely a demo project

you should ask in #coroutines

Some of the original kapt bugs have been marked as fixed targeted for 1.0.6. Does that mean that kapt3 will be the default in 1.0.6?

@yan ^^

@grandstaish Not yet, but the original kapt will become deprecated quite soon (at least, I hope so)

So if you have any issues with the new kapt, it’s the best time to let us know about it :)

Cool thanks for the info. No problems with the new kapt, all my issues are with the old one so I'm hoping for the same thing

When we can expect

1.0.6

to be released?

Also how to properly configure kapt3 in 1.0.6? Should I keep using

apply plugin: ‘kotlin-kapt’

?

apply plugin: 'kotlin-kapt'

is the way to go

we plan 1.0.6 RC for this week; the final release depends on the feedback we get

Will there be 1.0.7?

we don't know yet

eagerly waits for 1.1

I've updated to the latest -dev version and now I'm getting

Warning:(55, 71) Kotlin: '%' is resolved to deprecated 'mod' operator. Replace with '.mod' or add operator 'rem'

when using

%

on ints. Is this only temporary until

operator fun Int.rem

is added to stdlib?

also

Warning:(38, 21) Kotlin: Protected function call from public-API inline function is deprecated

when calling a protected function from a protected inline function. Is this right?