-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Allow casting to mutable trait objects. #5725
Conversation
r? @pcwalton |
@jdm -- I don't think this is quite the right way to handle the representation etc in the compiler |
I appreciate the feedback, but would you like to be a bit more specific? It's a bit hard to act on your comment. If this is covered by #5762, that's fine, but I would like to know what the next step is. |
Yes, sorry! That was brief. Let me expand. First off, I apologize, when I first read your patch I was somewhat mislead because you used the letters Anyhow, adding a mutability to ty_trait doesn't strike me as ideal, since it doesn't apply e.g. to I haven't had time to read over the patch in great detail to tell if you're covering all the necessary checks yet though, but it's a good idea to get the basic syntax etc in place. |
Getting the syntax in Rust is blocking my work on Servo. I still can't tell whether you're just asking for some renaming for clarity, or whether you're going to need to find some time to read through it more deeply before giving more directed feedback. |
@nikomatsakis Any further feedback on this? |
(though I would certainly prefer not using the mnemonic |
I'll rebase and rename the |
Rebased and renamed, and much more pleasant to read after Niko's trait changes! r? @nikomatsakis |
should_impl_trait - ignore methods with lifetime params Fixes: rust-lang#5617 changelog: don't lint should_implement_trait when an `Iterator::next` case has explicit parameters
No description provided.