# mapCatching for Collections in Standard Library?

**URL:** <https://discuss.kotlinlang.org/t/mapcatching-for-collections-in-standard-library/24428>\
**Category:** Language Design\
**Created:** [March 16, 2022, 8:00pm UTC](https://discuss.kotlinlang.org/t/mapcatching-for-collections-in-standard-library/24428 "2022-03-16T20:00:18Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![gkotula](https://avatars.discourse-cdn.com/v4/letter/g/edb3f5/32.png) [@gkotula](https://discuss.kotlinlang.org/u/gkotula)\
**Post date:** [March 17, 2022, 4:32pm UTC](https://discuss.kotlinlang.org/t/mapcatching-for-collections-in-standard-library/24428/3 "2022-03-17T16:32:50Z")

</div>

Thanks for the constructive feedback. You’re correct that this was a very simple thing to implement, and I like your take on a different approach to the same solution as well!

After reading the comment about Result, I decided to do some more digging and found this thread: [State of Kotlin.Result vs. kotlin-result? - #4 by Ilmir.Usmanov](https://discuss.kotlinlang.org/t/state-of-kotlin-result-vs-kotlin-result/21103/4) . It seems like the future of Kotlin Result and its use-cases is uncertain, so I’m willing to admit that this `mapCatching` suggestion may not be the correct thing to add to the standard library after all.

---

_[View the full topic](https://discuss.kotlinlang.org/t/mapcatching-for-collections-in-standard-library/24428)._