a = [0..100] and b = {"a":1, "b":2} are so simpl...

# announcements

[Ifvwm]

a = [0..100] and b = {"a":1, "b":2} are so simple and plain to use

[Karolis]

There are factory methods:

val a = listOf(1,2,3,4)
val a1 = mutableList(1,2,3,4)
val a2 = (0..100).toList()

val b = mapOf("a" to 1, "b" to 2)
val b1 = mutableMapOf(....)

[Karolis]

It might be that Kotlin doesn't use [] and {} because there are more than 1 implementation, (ArrayList, LinkedList) and they have mutable and immutable versions.

[gildor]

There are so many discussion about it and even KEEP proposal, please check it.
It’s not even close so simple as you may think
https://github.com/Kotlin/KEEP/pull/112

[Ifvwm]

we can do a=[1,2] in C, Haskell, Python, and Javascript, the most languages support that, why not java/kotlin?

[Ifvwm]

this KEEP seems good

[Ifvwm]

I wonder if kotlin will support that list comprehension stuff one day?

[Ifvwm]

no decorator, no generator, no comprehension, I think we're using some languages which stay on 90's

[gildor]

this KEEP seems good

No, it is not. It is full of problems

[gildor]

I wonder if kotlin will support that list comprehension stuff one day

It may of course, but we need good proposal for this. Existing one is definitely is not sufficient

[gildor]

no comprehension

Oh please, no

[Ifvwm]

why those modern langauges features are so difficult to implent on java/kotlin?

[gildor]

What kind feature exactly?

[Ifvwm]

the upside I said

[gildor]

there are many features

[gildor]

for example I’m strongly against comprehension

[gildor]

I think this syntax will not make anything good, it’s harder to read and write and already covered in kotlin perfectly using collection operators

[gildor]

If you want to know why collection literals are hard, just check disccussion

[gildor]

according to feature list that you mentioned, you probably have Python background, Kotlin is not Python, it has own history, own goals etc

I mean everything is possible to implement, it’s just a matter of reason and complexity of it

[Ifvwm]

I use several langauges

[gildor]

Kotlin is not Python

Or Kotlin is not LanguageX

[Ifvwm]

but those things are not every special stuff, like macro in lisp, pattern matching in haskell, continuation in scheme

[Ifvwm]

or Promise in JS, Future in Python

[Ifvwm]

I don't expect kotlint to implement those features, I know they may be difficult to kotlin

[gildor]

I’m not ready to discuss every particular feature and my opinion may not match Kotlin Team opinions, my point is simple:
To implement any new feature in the language you need very good reason and a lot of pros that overweight cons.
And if you have this reason and way to implement it, everyone may create KEEP proposal for Kotlin and discussed it with community and Kotlin Team

[Ifvwm]

fine