# Blog series: Dyn async in traits (continues)

**URL:** <https://internals.rust-lang.org/t/blog-series-dyn-async-in-traits-continues/17403>\
**Category:** language design\
**Created:** [September 18, 2022, 5:55pm UTC](https://internals.rust-lang.org/t/blog-series-dyn-async-in-traits-continues/17403 "2022-09-18T17:55:43Z")\
**Posts on this page:** 1\
**Showing post:** 52

<div class="post-metadata">

**Author:** ![Jules-Bertholet](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/jules-bertholet/32/10671_2.png) [@Jules-Bertholet](https://internals.rust-lang.org/u/Jules-Bertholet)\
**Post date:** [September 20, 2022, 10:24pm UTC](https://internals.rust-lang.org/t/blog-series-dyn-async-in-traits-continues/17403/52 "2022-09-20T22:24:03Z")

</div>

`async fn` futures compile into [state machines](https://tokio.rs/tokio/tutorial/async#async-fn-as-a-future). When the future is not actively being polled and making progress, all its local variables are stored inside the future. But the future is a value with a defined size, so all its contents need to have a defined size as well. So, to store a local variable inside a future, you need to know how much space it will take up at the point you create the future.

---

_[View the full topic](https://internals.rust-lang.org/t/blog-series-dyn-async-in-traits-continues/17403)._
