There are 'Unanswered Questions' that contain good code and do not get closed, because saying 'looks good' is really a comment, not an answer. Example: how-can-this-simple-handler-in-nodejs-be-improved *
There should be a mechanism to mark the question as answered.
Good code doesn't mean nothing can come out of a peer review.
Reviewing code doesn't always mean shred the OP's code to pieces, and propose better ways to do the same thing. It could just as well point out why every right decision was the right decision to make.
I don't have an example at hand, but if Eric Lippert were to post some piece of the C# compiler for peer review (slightly unlikely), I'm sure Jon Skeet would be able to review it and explain what makes this code be good code, and that would still be an awesome review post from which many people could learn many things.
I don't think unanswered questions should be automatically marked as answered.
The problem is, unanswered questions are not necessarily good code. Either nobody bothered to write an answer or nobody had something to say about it so far.
Upvoted, unanswered questions can stand on their own as upvoted, unanswered questions. They are good questions, but no one knew an answer to it. There's no problem with these and I don't think there needs to be a mechanism to handle them. In this case (CR) I think that these questions stand for "hey, that's interesting code, it's well written and I have no idea what you could improve", there's no problem there. Some day somebody might come along and see something.
Not upvoted (zero-score), unanswered questions on the other hand need to be investigated, because there's something wrong with them. No upvotes and no answers can only mean one of two things: Nobody looked at them or they're not good questions.
I don't see the need for an extra feature to handle these types of questions. The good ones stand on their own, the bad ones already get reviewed.
I think that sometimes, if there isn't an answer, just giving your opinion on what you would have done differently and why is enough of a review.
this leaves a very fine line on CR though, and where do we draw that line. once I start nit picking the code for formatting the way I like to see it I usually find something else in the code that would be more readable if written differently.
also, I think that even though a question doesn't have the readability tag listed on it, we should still review for readability, so suggest what would make the code more readable if it were 100 times more complex, and they used the same formatting.
things like that are good answers I think
Your example of https://codereview.stackexchange.com/q/6809 is an oddball. I would say that it's neither good code nor bad code. It's code that has been distilled down to a nearly trivial test case, so that it doesn't really do much of anything useful, yet still triggers a bug in node.js.
The problem is that the question is mainly about a bug in node.js itself, not in the posted JavaScript code. Therefore, nobody will be able to satisfactorily resolve the problem in the context of Code Review.
Therefore, I've nominated the question to be closed as off-topic.
