Cppcheck is raising another new false positive container out of bounds in the processor tests. Fortunately this time we can work around it easily without having to add an exception.
Note: emplace() would be better but cppcheck disagrees.
Details
Details
- Reviewers
PiRK - Group Reviewers
Restricted Project - Commits
- rABC5825de5b0cc5: [LINTER] Work around a cppcheck false positive
ninja check-avalanche arc lint
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Lint
Lint Not Applicable - Unit
Tests Not Applicable