I'm aware that this may have been posted again, but I couldn't think of any proper search terms to find it with, so forgive me if it's a duplicate and point me there please.

The question is simple, obvious from the title: Should we downvote questions that contain curious hoops or preemptively reject valid answers/solutions, if they don't explain the reasoning behind the rejection?

Examples are:

• I don't want to use [some functionality of the language or API I'm using].
• I want to do this in only one loop. (But doesn't count built-in iterating functions as loops.)

...anything in this style, as long as no explanation is included in the question. Raymond Chen describes it well enough here.

(I'm not talking about people who simply state the external requirements of their code and go on from there. I'm talking about people who avoid solutions that would actually solve the problem while meeting their requirements.)