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

Meeting Proposal: Generator optimizations, specifically size optimizations #3

Closed
JakobDegen opened this issue Apr 18, 2023 · 1 comment
Labels
meeting-proposal Proposal for a discussion topic at a team meeting

Comments

@JakobDegen
Copy link
Contributor

Summary

rustc often generates unnecessarily big futures. Ideally, we would like to fix this by being able to optimize pre-generator lowering async bodies almost as-if they were any other body. However, that presents some soundness challenges, see here for some discussion. There is a proposal for how to allow these optimizations.

How do we feel about this proposal? How confident are we that we will be able to accept this, or something with a substantially similar effect? Most importantly: What optimizations can we allow rustc to do when?

Reading

Nothing besides the links above. I can prepare a document for the meetin

Comment policy

These issues are meant to be used as an "announcements channel" regarding the proposal, and not as a
place to discuss the technical details. Feel free to subscribe to updates. We'll post comments when
reviewing the proposal in meetings or making a scheduling decision. In the meantime, if you have
questions or ideas, ping the proposers on Zulip (or elsewhere).

@JakobDegen JakobDegen added the meeting-proposal Proposal for a discussion topic at a team meeting label Apr 18, 2023
@chorman0773
Copy link

This meeting was held on 2023-05-02. Should this be closed for similar reasons as #5?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meeting-proposal Proposal for a discussion topic at a team meeting
Projects
None yet
Development

No branches or pull requests

2 participants