Anonymous user
Talk:Integer comparison: Difference between revisions
→when would two *integers* fail to compare?
(→when would two *integers* fail to compare?: new section) |
|||
Line 9:
You might as well ask what is the point of the task? If the point is to exercise the three comparison operators and observe that only one of them evaluates to true, then all of the posted solutions that use else if, switch, cond, or similar short circuit forms are incorrect. The reference solutions originally posted by the task author did exercise all three operators for any valid input without short circuiting. My Go solution was anomalously sophisticated, I know. It not only exercised all three operators, but went on to programmatically validate that exactly one operator returned true and that the other two returned false. —[[User:Sonia|Sonia]] 04:09, 28 June 2011 (UTC)
:Task says "test all three separately", not "use all three on all inputs". All three are used in the code right now, which fills the bill. If it were short-circuiting, the third test doesn't even need to be done. Even if you do leave all redundant tests in, there's no garantee an optimizer will keep them there anyway. --[[User:Ledrug|Ledrug]] 04:17, 28 June 2011 (UTC)
| |||