Asking a question typically leads to a handful of "shotgunned" answers. Yes, they do come immediately -- but the real story is, they are templated ("I'll fix it later, just lemme be the first to answer"), incomplete, and/or simply wrong.
A dozen explanatory comments later, the SO gun slingers finally understand the question and its implications. No, I really was NOT asking that. Neither that. Yes, that condition I mentioned in the question IS important and you cannot ignore it in your answer. You have an error there. That won't work.
Happened to me. And that person responding completely aside of the question voted to get my question closed and erased its answer. I was asking for axisting asynchronous signal slot library to avoid implementing mine. Another guy proposed to use QT and another one to use boost's signal which is not asynchronous. The later guy commented to the QT guy that boost was so much lighter and faster. Boost signal is known to be the less performant, but because its boost it must be the best. This guy also voted to close my question once I said I don't want to depend on boost. The question was finally closed and I implemented my self the signal slot lib with a perfect match to my requirements.
Asking a question typically leads to a handful of "shotgunned" answers. Yes, they do come immediately -- but the real story is, they are templated ("I'll fix it later, just lemme be the first to answer"), incomplete, and/or simply wrong.
A dozen explanatory comments later, the SO gun slingers finally understand the question and its implications. No, I really was NOT asking that. Neither that. Yes, that condition I mentioned in the question IS important and you cannot ignore it in your answer. You have an error there. That won't work.
And once that happens... silence falls.