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

early v late bound design and implementation background #94

Closed
lcnr opened this issue Jul 3, 2023 · 3 comments
Closed

early v late bound design and implementation background #94

lcnr opened this issue Jul 3, 2023 · 3 comments
Labels
deep-dive-proposal Proposal for a deep-dive discussion meeting T-types Add this label so rfcbot knows to poll the types team

Comments

@lcnr
Copy link
Contributor

lcnr commented Jul 3, 2023

Summary

summarize the status quo of early and late bound lifetimes, things we have to keep in mind going forward, and relevant current implementation details.

Rationale

We currently don't have a shared understanding of the status quo and where we want to go from here. We also don't have any good documentation of this. This meeting should both result in a useful document we can merge into the rustc-dev-guide and a foundation for future discussions, e.g. rust-lang/rust#103448

@lcnr lcnr added deep-dive-proposal Proposal for a deep-dive discussion meeting T-types Add this label so rfcbot knows to poll the types team labels Jul 3, 2023
@BoxyUwU
Copy link
Member

BoxyUwU commented Jul 3, 2023

Will also be good since the current rustc_dev_guide information on early/late bound lifetimes imo is lacking on information so it will be good to fill that out a bit with stuff from the deep dive doc

@BoxyUwU
Copy link
Member

BoxyUwU commented Jul 3, 2023

This was scheduled for 10/07/2023

@BoxyUwU
Copy link
Member

BoxyUwU commented Jul 11, 2023

This deep dive was had here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deep-dive-proposal Proposal for a deep-dive discussion meeting T-types Add this label so rfcbot knows to poll the types team
Projects
None yet
Development

No branches or pull requests

2 participants