News for hackers. Stuff that matters.
Re:The tragedy of 100% code coverage (2016) by computerex on Tuesday May 09, 2017 @11:45AM (#14300982)
Pitest has solved the halting problem?
Re:The tragedy of 100% code coverage (2016) by solatic on Tuesday May 09, 2017 @01:46PM (#14302270)
In the real world, you can't wait five minutes for the server to return a response. If the server returns the correct response after ten minutes, it's still wrong, unless the programmer has explicitly acknowledged that the procedure in question is a long-running procedure and has lengthened (but not eliminated) the time-out accordingly.

The halting problem is an irrelevant, Ivory-tower distraction in production code.

Re:The tragedy of 100% code coverage (2016) by mcv on Tuesday May 09, 2017 @11:52AM (#14301044)
Timeouts are not a perfect solution to the halting problem, but usually good enough.