# Kotlin Coroutines and (upcoming) Java Loom

**URL:** <https://discuss.kotlinlang.org/t/kotlin-coroutines-and-upcoming-java-loom/15819>\
**Category:** Language Design\
**Created:** [January 10, 2020, 11:45am UTC](https://discuss.kotlinlang.org/t/kotlin-coroutines-and-upcoming-java-loom/15819 "2020-01-10T11:45:46Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![rbygrave](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.kotlinlang.org/rbygrave/32/1433_2.png) [@rbygrave](https://discuss.kotlinlang.org/u/rbygrave)\
**Post date:** [January 31, 2020, 9:34pm UTC](https://discuss.kotlinlang.org/t/kotlin-coroutines-and-upcoming-java-loom/15819/4 "2020-01-31T21:34:02Z")

</div>

> [@darksnake](#):
>
> You should use search on this forum.

Yes, apologies. The discussion would be -

> [@How does Kotlin plan to integrate coroutines with Java Project Loom](https://discuss.kotlinlang.org/t/how-does-kotlin-plan-to-integrate-coroutines-with-java-project-loom/13413):
>
> [Project Loom](https://wiki.openjdk.java.net/display/loom/Main) will bring continuations and fibers (similar to kotlin coroutines) natively to the JVM in a not so distant future. It seems like they will be able to achieve to automatically convert blocking calls to suspending ones, when run inside a fiber. This magically makes things like Thread.sleep() or socket io suspending. There is no need to mark functions with a suspend modifier, annotation or similar. Also they have plans to provide some form of structured concurrency. For me the oppor…

> [@darksnake](#):
>
> The general consensus is that loom and coroutines solve different problems

Ok. Personally at the moment I see a lot of overlap so sorting that out is my homework. Thanks.

---

_[View the full topic](https://discuss.kotlinlang.org/t/kotlin-coroutines-and-upcoming-java-loom/15819)._