Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

The full reason text is

Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist"

but the "Questions asking for code" part seems to be gone in many minds.

Let's look at this question: User didn't show enough understanding to notice, that if compiler complains about not defined variable, the best solution would be to define it.
But it isn't a question asking for code, so that reason does not apply. Yet it already has a vote with that reason.
As I lately switched from answering question to close votes review, I can see it happens often. Probably because no other close reason fits better.


  1. Do you agree that such questions should be closed?
  2. What is a proper close reason in this case?
  3. How to help close-voters pick a right reason instead of abusing "minimal understanding" one?
share|improve this question
That one could simply be closed as "unclear what you're asking". The only reason it was answered is because the answerer was aware of a previous question and the code it had in it. – Bart Oct 10 '13 at 13:28
Don't hesitate to type in your own custom close reason. The willingness to take the time to do so is inversely proportional to the quality of the question. That's not "abuse". – Uphill Luge Oct 10 '13 at 13:41
up vote 13 down vote accepted
  1. Yes.
  2. The one stated. Minimal understanding of the problem includes not understanding clear compiler output.
  3. There is no abuse.
share|improve this answer
So the "Questions asking for code" reason part should be removed? – Tadeusz Kopec Oct 10 '13 at 13:37
That depends a bit on what you mean by "asking for code" @TadeuszKopec. I'd argue that any debugging question is implicitly asking for it. Even when there is no "please give me some code which...". – Bart Oct 10 '13 at 13:38
@TadeuszKopec - You can't have failing compilation without code... – Oded Oct 10 '13 at 13:39

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .