Skip to content

Issues: rust-lang/trait-system-refactor-initiative

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

Clear current search query, filters, and sorts
5 Open 3 Closed
5 Open 3 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Unsound associated type outlives bound due to lazy norm not-blocking-coherence An issue we can resolve after stabilizing the new solver during coherence
#59 opened Aug 14, 2023 by compiler-errors
1
hir typeck decision making now checks whether nested eq/sub obligations hold not-blocking-coherence An issue we can resolve after stabilizing the new solver during coherence
#23 opened May 29, 2023 by lcnr
1
should looking up the defined opaque types be structural or semantic not-blocking-coherence An issue we can resolve after stabilizing the new solver during coherence
#17 opened May 24, 2023 by lcnr
1
structurally resolve how does it work not-blocking-coherence An issue we can resolve after stabilizing the new solver during coherence
#15 opened May 19, 2023 by lcnr
Should we deeply normalize during writeback, or at the post-typeck places that need a "structurally resolved" type? A-normalization not-blocking-coherence An issue we can resolve after stabilizing the new solver during coherence
#3 opened Apr 13, 2023 by compiler-errors
2
ProTip! Add no:assignee to see everything that’s not assigned.