Based on this question: WPF Calculator Code
The question's code... works, according to the author. However, I quickly spotted multiple bugs. I know that Code Review is not there for fixing bugs. A single, minor bug shouldn't halt review process, however. But what do you do if there's a consistent misuse of a language feature?
In the linked question, the asker consistently resets arrays and strings by nulling them. However, he forgets to reinitialize them. This leads to a crash when he reuses the nulled variable. This leads to roughly 9 bugs (since there are 9 locations where this pattern is evident).
Do you ...
- Leave a comment stating the bugs and move on? No, says meta. Comments should be disposable, and a comment describing bugs is not disposable.
- Leave an answer only pointing out the bugs? Maybe, but we're not here to fix bugs, we're here to review code for other aspects.
- Do both, pointing out the bugs and reviewing the code? Earlier questions from meta seem to indicate that having to spend more time on a question discourages people from answering. So enforcing this means people just let buggy questions alone... except for the people who didn't notice the bug. This effectively means the bug will go unspotted.
- Vote to close, even although most of the code works, and it's just a minor error causing the bug?
I'm in a bit of a state of conflict regarding what to do. I picked option 3 because I believe helping people is the best course of action... but is that the right option for the site as a whole?