|
|
|
|
|
by josephg
741 days ago
|
|
I tried to fix a bug in Signal a few years ago. One part of the code took so long to do type inference on my poor old Intel MacBook that the Swift compiler errored out. I suppose waiting was out of the question, and I needed a faster computer to be able to compile the program. That was pretty horrifying. I’ve never seen a compiler that errors nondeterministically based on how fast your cpu is. Whatever design choices in the compiler team led to that moment were terrible. |
|
The tools team probably had ultra-fast Macs, and never encountered that.
It definitely sounds like a bug in the toolset. I hope that it was reported.