[clang-tidy] `modernize-use-ranges` invalid fix-it tracking issue
- Dominant language
- LLVM
- Stars
- 40.5k
- Forks
- 18.7k
- PR merge metrics
- PR metrics pending
Description
I've noticed we have quite a few open issues for invalid fix-its from this check, but many of them have similar underlying causes, so I've decided to classify them.
- `ranges::` algorithm has different return type than its `std::` analog:
- #127658
- #110223
- #124794
- `ranges::` algorithm has stricter concept requirements than its `std::` analog:
- #130684
- #110660
- #110655
- `ranges::` algorithm takes a full range where its `std::` analog takes just an iterator:
- #125740
Contributor guide
Research direction
Start by reading the linked invalid-fix-it reports: #127658, #110223, #124794, #130684, #110660, #110655, and #125740. The issue provides no file, test, or defined completion condition; a contributor would need to determine how these cases should be addressed before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100