3

I just closed one that could have been closed as this. However it's no hardship to just do a custom close with your own message. Do we really need a other close reason?


2

I was uncertain about this, however I must admit that this question is a good case in point. The problem was confusing = with == in code. This is not so much a typo as a misunderstanding of the C++ language, however if the question were to remain it would just be solving one person's coding problem, without really contributing to the general Arduino ...


1

I would vote for introducing this new closing reason. While the first sentence in the descriptions (with the "not reproducible" and "typo") leaves a bit open what exactly is meant, the second sentence ("less likely to help future readers") is the important part in most cases. I don't want to advocate against the first sentence ...


Only top voted, non community-wiki answers of a minimum length are eligible