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

I've seen several questions with 2-3 lines of code, that ask about why some obvious feature of language doesn't work, while code in question is perfectly valid and can be easily checked by, say just pasting it to console in case of JS (see this question for example: How to pass a variable in array index).

The only valid answer to those questions is "No, it works perfectly" and, IMO, those are useless to future visitor, since they don't even represent OP's misunderstanding, that could be shared by other visitors, who'd benefit from explanation, but really is just some kind of pilot or environment error (user tried to run different source? forgot to save before running test? whatever else having zero relation to code itself?)

What reason should be used to close such a questions? I choose "not constructive" for now, for the reason that questions with the single answer that basically means "you're just mistaken" cannot be constructive.

share|improve this question
"Too localized" would fit the bill I think. – Bart Aug 17 '12 at 13:18

You must log in to answer this question.

Browse other questions tagged .