Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking Issue for Generator Memory Usage #69826

Open
2 of 7 tasks
jonas-schievink opened this issue Mar 8, 2020 · 0 comments
Open
2 of 7 tasks

Tracking Issue for Generator Memory Usage #69826

jonas-schievink opened this issue Mar 8, 2020 · 0 comments
Labels
A-async-await A-codegen A-generators AsyncAwait-Triaged C-tracking-issue F-generators I-heavy T-compiler

Comments

@jonas-schievink
Copy link
Member

jonas-schievink commented Mar 8, 2020

(old issue: #52924)

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

Note that this issue is different from #69663, which tracks typesystem-level improvements regarding generators. This issue is purely about the code generation aspect.

@jonas-schievink jonas-schievink added A-codegen T-compiler C-tracking-issue A-generators I-heavy A-async-await F-generators labels Mar 8, 2020
@tmandry tmandry added the AsyncAwait-Triaged label Mar 17, 2020
tylerwhall added a commit to tylerwhall/rmp-futures that referenced this issue Apr 21, 2022
Unfortunately Rust doesn't inline async functions, even for tail calls.
Each level of indirection adds to the state size and that can scale with
the amount of calls into the library.

Remove some avoidable uses of async to help memory usage somewhat until
Rust fixes these issues.

rust-lang/rust#69826
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-async-await A-codegen A-generators AsyncAwait-Triaged C-tracking-issue F-generators I-heavy T-compiler
Projects
None yet
Development

No branches or pull requests

2 participants