Re:Don’t assume that safety comes for free: a Swift case study
by planteen on Tuesday December 06, 2016 @01:09PM
(#13116821)
> The fact that the overhead is only 2x for a tight inner loop should be a cause for celebration, not dire warnings. And as the author himself shows, it's very easy to disable overflow checking on a per-operation basis when you want to.
Agreed. This smells like premature optimization... on a problem that can be solved in O(1) time.
Agreed. This smells like premature optimization... on a problem that can be solved in O(1) time.