Apple Engineers Its Own Downfall with the Macbook Pro Keyboard

Re:Apple Engineers Its Own Downfall with the Macbook Pro Key... by fooker on Thursday June 28, 2018 @03:28AM (#17414789)

>Swift compile times have been improving as time goes on.

Swift compile times will never be close to ObjC or C compile times, no matter how much engineering goes into it. This is because of how the language is designed, it requires a typechecker which solves an NP hard constraint solving problem.

[ Parent | on HN ]

Re:Apple Engineers Its Own Downfall with the Macbook Pro Key... by woolvalley on Thursday June 28, 2018 @02:01PM (#17419110)

There is a whole bunch of low hanging fruit in the swift compiler as far as compile speed goes.

What swift compiler devs complain most about is about how operator overloading causes some sort of O(n^k) or worse check, because things like the '+' operator has dozens of implementers.

If your really worried about type inference slowing you down, you can write out all of your types like you didn't have type inference. You could even do it in an automated fashion like your source code was some sort of cache.

[ Parent | on HN ]

Re:Apple Engineers Its Own Downfall with the Macbook Pro Key... by 14113 on Thursday June 28, 2018 @04:23AM (#17415044)

Unlike C compilers which have no NP-hard problems to solve /s

[ Parent | on HN ]

Re:Apple Engineers Its Own Downfall with the Macbook Pro Key... by fooker on Thursday June 28, 2018 @08:06AM (#17416156)

You can write a C compiler without solving NP hard problems. You can even have pretty good optimizations.

[ Parent | on HN ]