-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Specify trait implementation, resolution, and coherence for 1.0 #11166
Comments
Accepted for 1.0, P-backcompat-lang. |
Visiting for triage: some progress has been made (particularly with all the new multi dispatch and associated type rules), but more needs to be done to fully specify everything. |
Nominating for removal from P-backcompat-lang. The spec/documentation side is probably covered by existing bugs; this issue should perhaps be closed. |
Assigning 1.0 milestone (specifically the writeup of the semantics -- I consider it polish). |
(I probably should have removed P-backcompat-lang from this ticket when I assigned this to 1.0 and categorized it as a polish issue. It is possible that writing up the semantics will expose bugs that would necessitate a change to the language specification, but it is highly unlikely, and probably does not justify the label.) |
closing; if someone can come up with a spec, great, but we're not going to block anything ourselves to do so. |
Refactor some of `dereference.rs` to util functions I've seen a few lints that need to be able to tell if changing the type of an expression would be a vaild suggestion. This extracts part of how that's done from `explicit_auto_deref`. changelog: None
Niko has a grab-bag of issues over on #5527.
There are a bunch of desiderata for traits in Rust, and we won't get to all of them for 1.0.
But we do need to firm up exactly what the core semantics are (for how trait matching is done, and what the limits are for the backward-compatible core of the language), with a specification against which we can compare the implementation.
The text was updated successfully, but these errors were encountered: