# Is Explicit Concurrency in Rust worth it?

**URL:** <https://trio.discourse.group/t/is-explicit-concurrency-in-rust-worth-it/217>\
**Category:** Structured concurrency\
**Created:** [September 9, 2019, 2:01am UTC](https://trio.discourse.group/t/is-explicit-concurrency-in-rust-worth-it/217 "2019-09-09T02:01:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![gortiz](https://yyz2.discourse-cdn.com/free1/user_avatar/trio.discourse.group/gortiz/32/136_2.png) [@gortiz](https://trio.discourse.group/u/gortiz)\
**Post date:** [September 11, 2019, 6:55am UTC](https://trio.discourse.group/t/is-explicit-concurrency-in-rust-worth-it/217/2 "2019-09-11T06:55:45Z")

</div>

There is thread in this forum where some people, including @njs, talk about the rust approach to concurrency.  
I think it really worth to take a look:

> [@Structured concurrency in Rust](https://trio.discourse.group/t/structured-concurrency-in-rust/73/14):
>
> Ah, but this is a radically different proposal than the one I wrote :-). In my proposal, remember, async is just a marker for the compiler that you want to opt-in to a coroutine / green-threads-like system – there’s no built-in connection to the Future machinery. In this approach, the only distinction between a sync function call vs. an async function call is that during an async call, the coroutine runner has the option of temporarily preempting this green-thread and letting some other green-…

---

_[View the full topic](https://trio.discourse.group/t/is-explicit-concurrency-in-rust-worth-it/217)._