Find the bug, not the style

by Leumas · for any

code
code review
debugging

Review the code below for DEFECTS ONLY — behaviour that is wrong, not style that is unusual.

For each finding give me:
1. The exact line or expression.
2. A concrete failing case: specific inputs or state, and what happens instead of what should.
3. The smallest change that fixes it.

Rules:
- Ignore formatting, naming and idiom entirely unless they cause a real defect.
- Rank by severity: data loss and silent wrongness first, crashes second, everything else after.
- If a finding depends on how the code is called, say what you are assuming.
- If you find nothing, say "no defects found" and name the two riskiest lines and why they are risky. Do not invent a finding to fill the space.

<code>
[PASTE HERE]
</code>

What it is for

Most review prompts return a wall of naming and formatting notes because that is what is easy to find. This one spends the whole budget on behaviour, and the "say so" clause is what stops it inventing a finding to look useful.