3 ms·

The issue OP mentioned is certainly not intractable to fix, and in general type inference doesn't have much to do with the stable ABI. The ABI work was about re

The issue OP mentioned is certainly not intractable to fix, and in general type inference doesn't have much to do with the stable ABI. The ABI work was about refactoring some compiler internals and implementing library evolution support, which as far as I'm aware is unique among statically-compiled languages: https://swift.org/blog/library-evolution/ https://swift.org/blog/library-evolution/. There was also a lot of work on code size improvements, runtime memory usage, and compilation time. The pace at which language features are added is not the only valid measure of language development.

anoncareer0212 6y ago
Those are all arguments your team has been repeating for a while, and I used to be amenable to, but am no longer given the amount of time that has elapsed. Something is pretty broken over there, and it's especially not charming to read the team chiming in with 'lol haskell too!' - can I bill you for the type inference crashes and workarounds I've had to do because no one bothered saying anything until August 2020? https://twitter.com/krzyzanowskim/status/1305579668104331264?s=20 https://twitter.com/krzyzanowskim/status/1305579668104331264... I'll be happy to admit I'm wrong when Swift UI 2021 is rendering lazy lists just fine on Mac and iOS, otherwise, its just me hearing about ARC optimizations for the 50th time and trusting it. https://twitter.com/jckarter/status/1305562770859933696?s=20 https://twitter.com/jckarter/status/1305562770859933696?s=20
- slavapestov 6y ago
  > can I bill you for the type inference crashes and workarounds I've had to do because no one bothered saying anything until August 2020? That's not related to the decidability of that specific algorithm in the generics implementation, though. Did you file bugs for the type checker problems you found? (I’m not being snarky; I’d love to take a look at them)

anoncareer0212 6y ago

Those are all arguments your team has been repeating for a while, and I used to be amenable to, but am no longer given the amount of time that has elapsed. Something is pretty broken over there, and it's especially not charming to read the team chiming in with 'lol haskell too!' - can I bill you for the type inference crashes and workarounds I've had to do because no one bothered saying anything until August 2020? https://twitter.com/krzyzanowskim/status/1305579668104331264?s=20 https://twitter.com/krzyzanowskim/status/1305579668104331264... I'll be happy to admit I'm wrong when Swift UI 2021 is rendering lazy lists just fine on Mac and iOS, otherwise, its just me hearing about ARC optimizations for the 50th time and trusting it. https://twitter.com/jckarter/status/1305562770859933696?s=20 https://twitter.com/jckarter/status/1305562770859933696?s=20

slavapestov 6y ago
> can I bill you for the type inference crashes and workarounds I've had to do because no one bothered saying anything until August 2020? That's not related to the decidability of that specific algorithm in the generics implementation, though. Did you file bugs for the type checker problems you found? (I’m not being snarky; I’d love to take a look at them)