# Why is slice a possible language future feature?

**URL:** <https://discuss.kotlinlang.org/t/why-is-slice-a-possible-language-future-feature/2475>\
**Category:** Language Design\
**Created:** [April 7, 2017, 8:51am UTC](https://discuss.kotlinlang.org/t/why-is-slice-a-possible-language-future-feature/2475 "2017-04-07T08:51:24Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![fvasco](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.kotlinlang.org/fvasco/32/1961_2.png) [@fvasco](https://discuss.kotlinlang.org/u/fvasco)\
**Post date:** [April 10, 2017, 6:54am UTC](https://discuss.kotlinlang.org/t/why-is-slice-a-possible-language-future-feature/2475/10 "2017-04-10T06:54:13Z")

</div>

> [@Ternary operator](https://discuss.kotlinlang.org/t/ternary-operator/2116/9):
>
> Writing code with the least number of characters is definitely non-goal for Kotlin.

---

_[View the full topic](https://discuss.kotlinlang.org/t/why-is-slice-a-possible-language-future-feature/2475)._