The below is an off-site archive of all tweets posted by @mjtsai ever

July 17th, 2014

@roopeshchander Yeah. Will be interesting to see how this evolves in Swift. Not sure I like the current way of wrapping in class methods.

via Tweetbot for Mac in reply to roopeshchander

@roopeshchander My main issue is that there's going to be 3+ lines of error-handling code for each line that does something that might fail.

via Tweetbot for Mac in reply to roopeshchander

@roopeshchander Right. That's why I think there needs to be a better way to do this in Swift.

via Tweetbot for Mac in reply to roopeshchander

@roopeshchander Choice between compiler help with safety and avoiding extra indentation.

via Tweetbot for Mac in reply to roopeshchander

@roopeshchander Yep. But is The Swift Way good? I’d love to see real examples of what people think is good Swift code for handling errors.

via Tweetbot for Mac in reply to roopeshchander

@roopeshchander Yeah, some people won't like that. I think it's worth it, and it's basically the same pattern Apple's macros have long used.

via Tweetbot for Mac in reply to roopeshchander

@felix_schwarz Good idea. I think that would work, although it requires more free disk space than I had (or a separate drive).

via Tweetbot for Mac in reply to felix_schwarz

@roopeshchander How does that work if I'm using "string" multiple times throughout the rest of the method?

via Tweetbot for Mac in reply to roopeshchander