-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Add lint for trait default impl removed #880
Add lint for trait default impl removed #880
Conversation
This is very close, and I'm excited to merge it! Re: the object safety issue you mentioned, I suspect you might accidentally have had the The A few action item suggestions:
|
Yeah, thanks for those suggestions, my bad. I normally do these things, and tend to be careful but this time I was actually in a rush to get it in, before I got busy with something else that I really overlooked doing those details
Thanks again for feedback! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're super close here! 🙌
I thought of an interesting edge case while reviewing the lint query, and I think we want to make a small tweak in approach to handle it properly.
There are also a few more typos, test case improvements, and general little points of friction that you could practice catching on your own by self-reviewing your code in the GitHub UI. The fewer comments and fixes I need to apply in code review, the faster and more efficiently we'll both ship code. Fixing things in code review is very inefficient results in fewer/slower merged PRs, so it can be frustrating and wasteful for you, me, and the community as a whole.
That said, don't worry about things that have already happened, and just seek to improve going forward! Becoming better every day is the goal, everything else is icing on the cake. As long as you're interested in improving your skills, I'll be happy to point you in the right direction to do so quickly and efficiently.
Go team! I think we're one last iteration away from shipping this 🚀
Add test cases for ensuring edge cases around sealed/non sealed minor typos
I am 100% willing to keep improving my skills, so I appreciate the feedback. I will be more careful on the next PRs , so that the content of discussion should be the technical sides, not the typos as i can imagine that's extremely frustrating. Funny because normally I contribute code, and here is mostly wording thus making it more difficult 😛 But on test cases from your suggestions, I added:
I hope that this one should be the one. Thanks for the patience!! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent work! Merging 🚀 Thanks for putting this together!
// Default trait method impl is removed, but it's sealed. The fact that it's sealed dominates, | ||
// thus having its default impl removed is not a problem since it was never possible to | ||
// implement it, should not be reported |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an excellent explanation, well done!
Btw, I recently created a Discord server to make it easier to coordinate |
Should add another lint for #870, particularly
non-sealed trait removed a default impl for a trait method
. Fixes #294.I am not sure if the
object_safe @filter(op: "=", value: ["$true"])
line is needed, since otherwise it would raise another lint. I thought that it could be aFalse Positive
, since at least if i try it locally, I only get thewarning
if it returnsSelf
, like so:Anyways, otherwise any feedback happy to change. Thanks!