While I understand the logic behind reviewing answered questions in the close queue - that is, bad questions should still be closed or put on hold in order to discourage people from asking them, even if they have been answered already - there are three glaring problems with this idea:
- Many of the questions that are appropriate to close, are from new users with a reputation of 1. Completely new users probably won't be discouraged by the fact that we are putting thousands of questions on hold, because they have never asked a question before and so they simply aren't aware of this torrent of closes.
- Putting a question on hold has the best deterrent effect if it happens before any answers are provided.
- Putting a question on hold is more helpful to the user than nothing at all, if no answers have been provided. If, on the other hand, a useful answer has already been provided, putting the question on hold is not really directly helpful, although it does help to enforce community norms.
It's very frustrating that I have voted to close unanswered questions that are not even about programming and yet are still unclosed after 7 days, probably because their tags have too few followers - while at the same time I'm being asked to review questions for closing that have up to 9 answers, which seem kind of less urgent to close.
Putting unanswered questions on hold would actually help users to ask appropriate questions in appropriate venues and get appropriate answers. Why can't unanswered questions be prioritised in the close queue? Maybe not with a 100% weighting over answered questions, but at least with a heavier weighting than they have at the moment?
If this is not desired, can we at least have a filter to enable those of us who care about this to opt to review unanswered questions first in the close queue?