4 ms·
On top of that, his complaints about error messages are... well... not sure the word I'm looking for. I don't even know swift and those error messages don't lo
by jharger 11y ago
On top of that, his complaints about error messages are... well... not sure the word I'm looking for.
I don't even know swift and those error messages don't look that bad to me. The only thing that seemed slightly odd is the Int(...) < Int(...) one... but again I don't know swift, so maybe that's just a badly formed expression (like attempting to compare object references or something).
- deleted 11y ago[deleted]
- kennywinker 11y agothe clang errors Xcode gives you when using ObjC are generally quite helpful. They should be, as they represent decades of development effort (on GCC and then clang). Swift is notably less verbose, but mostly it's just as an ObjC dev you've developed years of experience and you know what that EXC_BAD_ACCESS probably means you forgot to do... with Swift you're a beginner again.