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.

Sign up for GitHub

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

Jump to bottom

Design meeting: Freeze in bounds (RFC 3633), part 2 #313

Open
traviscross opened this issue Feb 27, 2025 · 0 comments
Open

Design meeting: Freeze in bounds (RFC 3633), part 2 #313

traviscross opened this issue Feb 27, 2025 · 0 comments
Labels
meeting-proposal Proposal for a lang team design meeting T-lang

Comments

@traviscross
Copy link
Contributor

traviscross commented Feb 27, 2025 •
edited
Loading

Summary

There's an outstanding RFC for Freeze in bounds:

We had a design meeting on this awhile back:

We're blocking this on three issues:

  • How should the SemVer hazard be treated?
  • How should PhantomData<T> behave regarding Freeze?
  • Should the trait be renamed?

@p-avital is working on a document for us. Perhaps we can take another pass at this.

About this issue

This issue corresponds to a lang-team design meeting proposal. It corresponds to a possible topic of discussion that may be scheduled for deeper discussion during one of our design meetings.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
meeting-proposal Proposal for a lang team design meeting T-lang
Projects
T-lang design meeting schedule
Status: Needs triage
Milestone
No milestone
Development

No branches or pull requests
1 participant
@traviscross