Filip Dolník

Closing for no activity. Let us know if the issue persists with the latest SKIE version, and we will reopen the issue.

I was able to work around a similar issue by first altering the table `foo` using the `ALTER TABLE`. For example: ``` ALTER TABLE Foo RENAME TO FooTmp; ALTER TABLE...

Hi! First of all, I want to say that I really like this idea, and I've been missing this feature in Kotlin for a while. I have one question/comment about...

> > As for the first issue, I can't think of any situation where this new syntax would create a problem because I don't think Kotlin has any expression and...

> If we are in a codebase that uses star-import (and many of them do), the arrival of this language feature with `.VALUE` syntax would mean: > > * Replacing...

> User expectations: one very important difference with Swift is that we take a restrictive route, in which we are very clear about when you can expect types to guide...

> Let me reiterate that Swift had that syntax from the beginning, so whatever the chose back then has been stable. We have a different starting point, with lots of...

@serras Thanks for looking into how the `.value` syntax could be implemented. I tried something similar yesterday and also concluded that the best way is to add another derivation rule...

>To give another example of this difference, you need to write: > >```kotlin >fun f(): Status = Ok >fun g() = Status.Ok >``` > >because in `g` we have no...

>I realize the reason behind the trap introduced by .value is that it occurs to be the first token after a value, and whether it's valid also depends on whether...