Incorrect comparison function - violates strict weak ordering
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 65
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
This comparison function violates the requirement for Strict Weak Ordering and will cause undefined behaviour/corruption inside the map.
Consider colours A(255, 0, 0) and B(0, 255, 0). Both A < B and B < A will return true.
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
Open the linked questions/qmap-qcolor-32512125/main.cpp lines 4-8 and inspect the colour comparison function. Check it with the A and B values given in the issue; done means the comparison no longer reports both A < B and B < A, preserving valid map ordering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100