- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1.8k
Add linter for a single element for loop #6109
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 linter for a single element for loop #6109
Conversation
| Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @flip1995 (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. | 
e8307d3    to
    32cab51      
    Compare
  
    cb2be56    to
    7babff8      
    Compare
  
    | ping @flip1995 | 
    
      
        1 similar comment
      
    
  
    | ping @flip1995 | 
| Sorry for taking so long. I currently have 15 PRs I'm actively reviewing/triaging besides doing other organizational stuff for Clippy. I usually review on weekends, so pinging doesn't really help to speed up my reviews. | 
| ☔ The latest upstream changes (presumably #5727) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:  | 
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.
Thanks for the contribution and welcome to Clippy!
58a0cbc    to
    1a1f347      
    Compare
  
    | Hi @flip1995, sorry for the ping, is just something that I do after a couple of days if a PR does not get a review, but since you mainly review PRs during the weekends I'll stop ping here. Sorry for the bothering! | 
220a4a6    to
    094e0f2      
    Compare
  
    094e0f2    to
    51c7834      
    Compare
  
    51c7834    to
    de937ab      
    Compare
  
    Signed-off-by: Patrick José Pereira <[email protected]>
Signed-off-by: Patrick José Pereira <[email protected]>
de937ab    to
    ba1ca19      
    Compare
  
    | ping @flip1995 | 
| @bors r+ Thanks! Sorry for taking so long. I'll start a new job in a new town next month and have little time for reviews currently. I hope it settles down soon and I have more time and energy for Clippy again. | 
| 📌 Commit ba1ca19 has been approved by  | 
| ☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test | 
| Hi @flip1995, thank you for the review, I was just a bit worried about the hacktoberfest schedule. | 
| IIUC for hacktoberfest only the opening date of the PR is relevant. 😉 | 
changelog: Fixes #1540, check for vectors that contain a single element in a for loop