3 ms·
Next, do Swift’s. So unbelievably awful, and more error-prone because of it.
by KerrAvon 5y ago
Next, do Swift’s. So unbelievably awful, and more error-prone because of it.
- jshier 5y agoSwift 5.6 already got a few changes, with more on the way.
- saagarjha 5y agoThey’ve improved some of the things, but the ergonomics of “I have an UnsafeXPointer and I want an UnsafeYPointer” could be significantly improved. Plus, Swift really needs better documentation as to how aliasing works when external code captures a pointer and reinterprets it. My current understand is that it’s far more lenient than what C allows (basically exposing LLVM’s model directly) but this isn’t really documented anywhere that I could find.