Including good suggested fixes is certainly better than not. But no suggested fixes are better than bad suggested fixes. Finding problems is a different skill set than proposing solutions. Letting people with these complementary skill sets coöperate in improving something seems to be better than requiring one person have both. The perfect is the enemy of the good.
I'm not sure why emphasis on failure is a problem, when that failure is precisely what is being communicated. However, the comment certainly does look a lot more unfriendly in light of the responses. Perhaps I was too kind to "i'm confused as to why this project even exists", because I don't understand why I would ever want "code snippets" myself.
As a product person, I want to hear someone's proposed solutions even if their ideas are crap. The reason is that sometimes their proposed solutions help me understand the problem better, and sometimes there is an aspect of their proposed solution that makes it into the final solution too.
I'm not sure why emphasis on failure is a problem, when that failure is precisely what is being communicated. However, the comment certainly does look a lot more unfriendly in light of the responses. Perhaps I was too kind to "i'm confused as to why this project even exists", because I don't understand why I would ever want "code snippets" myself.