Tracking Issue for Coroutine Memory Usage

[jonas-schievink]

(old issue: https://github.com/rust-lang/rust/issues/52924)

This issue tracks ideas for reducing the memory footprint of coroutines.

• [ ] https://github.com/rust-lang/rust/issues/59087 – Generator size: borrowed variables are assumed live across following yield points
• [ ] https://github.com/rust-lang/rust/issues/62321 – size_of_val in a generator can make the generator bigger
• [ ] https://github.com/rust-lang/rust/issues/62575 – Better greedy layout computation for generators
• [ ] https://github.com/rust-lang/rust/issues/62952 – Copy trait defeats generator optimization
• [ ] https://github.com/rust-lang/rust/issues/62958 – Async fn doubles argument size
• [x] https://github.com/rust-lang/rust/issues/66100 – [codegen] Unnecessary panicking branches in resumption of infinite generator (stored in static variable)
• [x] https://github.com/rust-lang/rust/issues/69815 – Generators should use smaller discriminants

Note that this issue is different from https://github.com/rust-lang/rust/issues/69663, which tracks typesystem-level improvements regarding coroutines. This issue is purely about the code generation aspect.

[pnkfelix]

Visiting during T-compiler backlog bonanza. This isn't the same kind of "tracking issue" that we associated with the C-tracking-issue label (in terms of a specific feature being designed)

@rustbot label: +metabug -C-tracking-issue

[oli-obk]

This is now being tracked as a github project: https://github.com/orgs/rust-lang/projects/21/views/1?layout=board

[Thomasdezeeuw]

This is now being tracked as a github project: https://github.com/orgs/rust-lang/projects/21/views/1?layout=board

@oli-obk that link is either incorrect or the project is private, in either case it doesn't work

[oli-obk]

hmm

Only organization owners can change project visibility.

Looking how to fix that, sorry