or one of the other candidates in the KEEP

So why is it redundant?

It would feel redundant to add

=>

now that

get() =

works

adding

=>

if

get() =

didn't work, wouldn't feel redundant

* a bit redundant

I see now, maybe you're right and it's really redundant

I'm not against the idea of

=>

in general, because it is more concise

@dmitry.petrov What's the reason for https://github.com/JetBrains/kotlin/commit/4c47d77a9fe986a597c3fd77d0317c1ac1343b6f?

We have no "species scopes" in Kotlin yet (scopes that capture type parameters, but not instances). Full support for nested TAs requires "species scopes". That's a rather strong change for which we have no resources in 1.1 time frame. If we introduce nested TAs now with some limited support, fully supporting them later will be a breaking change. So we decided to postpone them until after 1.1 is stabilized. Yes, that's a disappointment. Sorry about that 😞

does that mean code that previously worked with 1.1-M02 will now break?

e.g.

class Foo<T> {
    typealias Bar = (T) -> Unit
}

Yes.

😕

Same thing here.

I had a perfect usecase for that in my project

I was pretty much convinced we have to do that in 1.1. However, sometimes we can't have good things right now 😞.

and leaving it as it is and restricting some "weird stuff" until later isn't an option?

Yes, otherwise introducing constructors for such aliases later would be a breaking change.

I trust you to have the better understanding of this, so okay

I get notification saying 1.1-M03 is available though I set EAP 1.0.x as the update channel.

@yole ^^

It's ok to have it. Just wanted to let you guys at JetBrains know, in case it's not intended. 🙂

So 1.1-M03 isn't out yet?

I think it's officially out when there's a blog post available 🙂

Yea... But as I wrote above, I got the notification that it's available. Anyway, it doesn't seem out yet.

I guess they retracted it, it is not available for me anymore

Ah, I missed that one 👍

gradle 3.2 is broken for android projects on 1.1-M03 @alexey.tsvetkov

there was a known issue, not sure if it's supposed to be fixed already