[BUG] Fix clang-tidy errors properly after removing `// NOLINT` tags from the offending lines
Open
Nobody has claimed this yet.
bug
inactive-30d
inactive-90d
- Dominant language
- Cuda
- Stars
- 1k
- Forks
- 251
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
As part of PR #85 I introduced // NOLINT tag to restrict the amount of interface changes due to tidy error fixes. Over time, we should remove most of these tags and fix these errors properly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing PR #85 and locating the remaining // NOLINT tags associated with clang-tidy errors. Run clang-tidy on the affected code, then remove the tags and fix the underlying errors properly; completion means the relevant errors are resolved without those suppressions.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100