A modern programming language that makes developers happier.

kotlinlang

Please point me elsewhere if this isn't the best channel, but I'm wondering why `IntRange` and `IntProgression` don't support the `get()` operator like `List` does. <https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.collections/-list/get.html>

I'm guessing because lists are usually backed by arrays that can support a get in constant time. Ranges and progressions rarely need a get and a get would provide no performance benefits over the client iterating over the range

Alternatively you write it yourself. For some implementations you could easily write a constant version. 

Thank you, <@UG7GAS1QV>. As you probably know, there is an `elementAt()` method.
Looking at the <https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.sequences/element-at.html|documentation>,  I see that `elementAt()` is terminal, which answers my underlying unstated question of the difference between `get()` and `elementAt()`.

<@U01JRLZH77T> You're right, but this was meant as a why-did-they-do-that question, not a how-do-I-do-that. Sorry for not being more clear.

I was not aware. I assume you meant this one <https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.collections/element-at.html> which doesn't have docs about being terminal as terminal is a concept specific to sequences.

For collections that have a get method, elementAt just delegates to get
<https://github.com/JetBrains/kotlin/blob/7a7d392b3470b38d42f80c896b7270678d0f95c3/libraries/stdlib/jvm/src/generated/_ArraysJvm.kt#L35>

<https://github.com/JetBrains/kotlin/blob/7a7d392b3470b38d42f80c896b7270678d0f95c3/libraries/stdlib/common/src/generated/_Collections.kt#L105>