List<C extends (A intersection B)>

would that also be weird, but parseable as

List<(C extends A) intersection B)>

? =p

Untitled.kt

Huh, that's an interesting trick, although I tend to think of some kind of structure typing being required for that to be generally useful.

@clifton: I’ve been following Ceylon since the very beginning (like Kotlin). It’s a very interesting language that pushes the type system in new and interesting ways. I still follow it but I agree with @evanchooly that at this point, it seems to be in a dead end

The native support of sum and intersection types has opened up all kinds of interesting properties which are now being picked up by dotty (another dead end in my opinion), so it’s worth following if you’re interested in programming languages in general (and Gavin is wicked smart).

Interesting... Indeed lots of these languages seem new and exotic to me

To some, Kotlin does too

Kotlin makes far more sense than most

But I'm confident it will drop the novelty status pretty soon, once it gets traction

we already have Kotlin++, it's called Scala 😛

Oh common that's rather --

@nimtiazm You mean like Kotlin |0>?

sometimes -- is ++

Lols

so I'm not disagreeing here

Scala had a chance and it beautifully destroyed it

I'm pretty sure you can redefine -- to ++ in Scala

So in this case, @kevinmost is right on multiple levels 🙂

Nothing stopping you from doing

operator fun Int.unaryMinus(): Int = unaryPlus()

in Kotlin, too

That's the irony. Nobody might really understand your Scala. See?

@kevinmost Fair

hmm... does that work, actually?

@kevinmost (kotlin+)+ or kotlin+++ is then also OK?

Two shakes and I'll let you know

wait,

unaryMinus

isn't

--

I got my things mixed up.

--

is

dec

Wait, don't you mean

Int.inc()

Yeah, I just caught that too

@kevinmost Didn't work.

fun main(args: Array<String>) {
    var five = 5
    five--
    println(five)
}

operator fun Int.dec() = inc()

Printed 4