Swift 3 is still upsetting.
@av I enjoyed migrating to Swift 3. *cough*
The converter fucked everything up, so I hand converted 24000 lines of code.
@piecritic yea I did the BIG mistake of running the converter several times - instead of fixing more stuff or not doing anything after the first time it just re-fixed things the wrong way... so I had to fix its fixes....
@av it totally fucked up enums in unspeakable and non-deterministic ways. I was actually amazed at how much damage it managed to do.
@piecritic for me it just lowercamel-cased all the enums I had but then didn't bother to also update all the places that used those enum cases... so suddenly I got hundreds of "case not exists for enum etc.."
@av the biggest issue I had wasn't even that. It was that all the popular projects took the opportunity for a major version bump to make major API changes as well, so there was no way I could confirm after the conversion that everything would work as it should.
Days of testing, days more of surprises being fixed.
@piecritic it almost felt like projects where changing for the sake of changing.... but all that would be no brained if Xcode would build fast and won't freeze/crash...
@av I had Xcode memory leak so hard today the OS paused random processes and asked me to intervene, lololol
@piecritic What went bad? I found swift 2 largely non-evil after writing a couple apps with Obj-C. But that was in 2015 and I haven't compiled anything since.
@photopuck it still is fairly easy to make it segfault, and its type checker is so broken it blames closures for every type issue it finds. Or it recommends replacing a type with '_' which is obviously wrong.
@piecritic I just needed about 20 classes from a commit about a year ago - but it took 2 days only to compile them cuz I had to update them to Swift3 🙄