4 ms·
I agree with you, but this thread is full of people thinking it's a good idea because they or their colleagues are prone to that kind of silliness. For people
by bluefox 7y ago
I agree with you, but this thread is full of people thinking it's a good idea because they or their colleagues are prone to that kind of silliness. For people who write C or C++ every day it's stupid compiler second-guessing, and it can also create issues for generated code, but this thread shows that our tools may need adjustment to better deal with today's level of incompetence.
- colejohnson66 7y agoWhy would you write 2 xor 16 in instead of just 18? And if it’s generated code, wrap it in a pragma to disable the warning
- bluefox 7y ago> Why would you write 2 xor 16 in instead of just 18? Why would you beat up your wife instead of expressing your anger using words? > pragma to disable the warning Proposal to change "#pragma" to "#panacea" and be done with any argument related to compiler-specific behavior.
- dang 7y ago> Why would you beat up your wife instead of expressing your anger using words? Not cool. Please don't post like this to HN again. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- bluefox 7y agohttps://en.wikipedia.org/wiki/Complex_question https://en.wikipedia.org/wiki/Complex_question Also, the excuse might be the same in the two questions: brute force may be less demanding than particular calculation.