# State of Kotlin.Result vs. kotlin-result?

**URL:** <https://discuss.kotlinlang.org/t/state-of-kotlin-result-vs-kotlin-result/21103>\
**Category:** Language Design\
**Created:** [March 6, 2021, 7:54am UTC](https://discuss.kotlinlang.org/t/state-of-kotlin-result-vs-kotlin-result/21103 "2021-03-06T07:54:45Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Ilmir.Usmanov](https://avatars.discourse-cdn.com/v4/letter/i/e495f1/32.png) [@Ilmir.Usmanov](https://discuss.kotlinlang.org/u/Ilmir.Usmanov)\
**Post date:** [March 18, 2021, 2:36pm UTC](https://discuss.kotlinlang.org/t/state-of-kotlin-result-vs-kotlin-result/21103/5 "2021-03-18T14:36:44Z")

</div>

Change of plans. We will allow returning `kotliln.Result` from functions. For checked exceptions there will be another feature, which does not involve `kotlin.Result`. Reason is simple: `kotlin.Result` does not allow specific exceptions, which is needed for checked exceptions. It is not yet clear, how checked exceptions will look like. The best candidate is contextual receivers.

---

_[View the full topic](https://discuss.kotlinlang.org/t/state-of-kotlin-result-vs-kotlin-result/21103)._
