3 ms·
Quite often (at least in HPC) you equally care about correctness AND complexity/memory-usage and performance: there's no point being fast if the result's wrong,
by berkut 5y ago
Quite often (at least in HPC) you equally care about correctness AND complexity/memory-usage and performance: there's no point being fast if the result's wrong, but equally, there's often no point being correct if the result takes ages to calculate, as the premise is calculating things in a particular time frame for the complexity budget of an algorithm.
- ithkuil 5y agoComputing wrong results is rarely ok. But what matters is not only whether something is wrong but more often what are the consequences of being wrong. For example bugs in graphics rendering in games may be annoying but may cause long lasting effects such as data corruption, so it may be argued that whatever tooling you use to program your graphics can tolerate a bit more of sloppiness than the tooling you use to program your filesystem layer.