2

SWIFT 3 sucks! SUCKS I TELL YOU! swift 3 changes the NSError class to its own Error class, now the categories (i.e the extensions) that I have added to the NSError class (like convenience inits and NSDictionary map to my own variables) are ALL LOST !!! MORE THAN 100 LINES OF CODE LOST!! because of this piece of shit mutation of the DATA TYPE ITSELF!!! when objective C code is used in Swift (using the mix-match technique) DONT UPGRADE TO swift 3.0 GUYS DONT DO IT!!! especially if you have legacy code in your project !!

Comments
  • 0
    I've been putting off the 3.0 migration for as long as I can...been sticking to 2.3. I'm scared of how many things will break and/or have incorrect upgrade suggestions (by far the worst offender during upgrades).
  • 1
    @emes001 In the end I fixed this by casting Error to NSError at every place I use NSError such a pain in the ass though!
Add Comment