If you're specifically asking about the wording of the close reason, then no, I don't think it is broken. The reason reads like this.
Questions containing broken code or asking for advice about code not yet written are off-topic, as the code is not ready for review. After the question has been edited to contain working code, we will consider reopening it.
Clicking on the link for “broken code” directly takes you to this meta post that states prominently:
Does your question contain something like:
- … runs … but it gives the wrong answer …
- … I tried … but sometimes …
- … works great when I do …, but when I do …
- … it works fine, but I also need it to do …
If it does, then your code does not work in the way that you expect, or need.
Broken code is code that:
- cannot possibly compile even if other dependencies are included
- fails to run (crashes, throws exceptions, core-dumps, segfaults, etc.)
- produces results that are obviously incorrect
I don't see how this could not be clear enough about the fact that code that “is not broken but just doesn't produce the correct answer” is off-topic here. It seems that some people might take “broken” as “does not compile” but they should click the link and find out about their mistake. It is not common to call code that produces incorrect results anything but broken and I don't think we should bend the terminology used here for those few wo are confused about this.
That said, we should be careful when posting comments without the link or only paraphrasing in a way that might be less clear. It also seems that the wording on the What topics can I ask about here? page could be improved. All it currently has to say is
If you are looking for feedback on a specific working piece of code from your project in the following areas…
That might indeed be too vague but might also be beyond the scope of this meta question.
Another problem is that in order to realize that your code is broken, you actually have to do some work. Some people just post what they think is working code when it has severe bugs. Spotting logic errors is also part of code review so that's not a problem per se but it would be undesirable if we would steer people into remaining silent about the known issues of their code just to prevent their question from being closed.