-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
tracking issue for "chalkification" #48049
Comments
#48411 is done |
For my own searchability, I'm adding the plain word chalk. |
See also the WG-traits meeting doc which has been updated more recently. |
For reference, some substantial work on universes has recently been merged: #55517. |
What's left here? It looks like all the checkboxes are ticked. |
Until the question is answered, this tracking issue no longer tracks the issue. |
Until @nikomatsakis corrects me otherwise, I'm going to assume that #59490 blocks this and thus this tracking issue once again tracks the issue. |
Hard to summarize. We're working on making an approachable roadmap and summary on the https://github.com/rust-lang/wg-traits repository, but it's not quite there yet. |
Ping for status 🙂 Very excited for this (especially for implied bounds)! |
I recently looked and as I recall, roughly ~60% of (ui) tests were passing with |
Visiting for backlog bonanza. @rustbot label: S-tracking-needs-summary |
@rustbot label: S-tracking-impl-incomplete |
Visiting for types triage. We feel like this issue doesn't buy us much. It feels like a general "things to make rustc behave like chalk", which is probably better tracked through individual issues + a project. We're currently pursuing a-mir-formality, which will have implications here anyways. |
This is a place holder for various refactorings going on in the trait system aimed, ultimately, at improving efficiency and correctness. Some of the key goals include lazy normalization, better caching, and removing many of the trait-related overflow errors. I plan to flesh out details better here as we go.
The text was updated successfully, but these errors were encountered: