4 ms·
The Swift compiler is still the only compiler I know that times out. Algorithmic complexity is such a large part of a fancy university education that I just do
by danielscrubs 2y ago
The Swift compiler is still the only compiler I know that times out.
Algorithmic complexity is such a large part of a fancy university education that I just don’t understand how they could come up with swifts feature set if they knew it would come back and royally bite them.
What an I missing? What is the backstory?
- kridsdale1 2y agoIm guessing: The post Next Apple is entirely dependent on llvm. The hardware is tuned to its outputs. The devX is based on generating it. Apple 15 years ago was getting worried people are not learning C in school anymore. They were learning python and ruby and js. Swift exists as a way to market llvm as a tool chain to that market of programmers. My views are informed by years of talking to Apple and build-for-Apple engineers.
- int_19h 2y agoC# can also do that - there's a general problem there with combinatorial explosion when you combine function overloading with generics and lambdas.
- chabska 2y agoThe Swift devs drank the koolaid that Java's method of implementing generics using type erasure is bad, so they implemented Swift's generics by concrete specialization. Turns out that caused a lot of complexity in type lookup.
- danielscrubs 2y agoInteresting, I guess the language is now supervised by a committee which means there is no chance in hell it will be fixed.