Wade Tregaskis (Hacker News): In a nutshell, the problem is that Swift’s Clock protocol has significant overheads by design. If you look at a time profile of code like this, you’ll see things like[…]That’s a lot of time wasted in function calls and struct initialisation and type conversion and protocol witnesses and all that guff. […]