-
Notifications
You must be signed in to change notification settings - Fork 802
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
Seal traits inside impl_
submodule
#3908
Comments
I labelled this "Good First Issue", as this is an internal refactoring which would be great to have. A "sealed" trait has a private supertrait, thus making it possible to implement outside the crate. All of the |
@davidhewitt I am happy to have a look at this |
Brilliant, thanks 🙏 |
@davidhewitt quick question, are there any particular reasons something should be or should not be moved? Or is it ideally everything should be moved from |
I don't think we should be moving any code, this issue is about upgrading |
I see, so those traits that could be used by the user need to be |
Yes, in principle many things inside |
Thank you for your patience, I was occupied by EuroPython preparation in the last few weeks. I plan to pick this one up again this weekend or next week. |
I think the next step along here would be finding traits which make use of the |
@davidhewitt @LilyFoote is this issue closed? It seems so to me |
I think there are still lots of traits in |
Cool, I will go treasure hunt when I got the time! |
Off the back of #3897 (comment)
Should we review the traits inside the
impl_
submodule, check which ones can be sealed, and do that? It's a reasonable safety mechanism to prevent users from trying to implement those things.The text was updated successfully, but these errors were encountered: