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

discuss "incorrect implied bounds in wfcheck" #99

Open
nikomatsakis opened this issue Sep 11, 2023 · 2 comments
Open

discuss "incorrect implied bounds in wfcheck" #99

nikomatsakis opened this issue Sep 11, 2023 · 2 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

@nikomatsakis
Copy link
Contributor

Summary

As discussed in the Sep 11 t-types meeting, we want to have a deep-dive discussion of rust-lang/rust#109763 to better understand the problem and discuss the best solution. The goal would be to cover what the problem is, what the proposed fix is, and specifically to understand the impact this could have on bevy consumers and how that might be mitigated.

Rationale

Broad impact.

@nikomatsakis nikomatsakis 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 Sep 11, 2023
@alice-i-cecile
Copy link

I've made a writeup of the issue at bevyengine/bevy#9808

@jackh726
Copy link
Member

jackh726 commented Dec 4, 2023

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

3 participants