@roopeshchander Yeah. Will be interesting to see how this evolves in Swift. Not sure I like the current way of wrapping in class methods.
@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.
@roopeshchander Right. That's why I think there needs to be a better way to do this in Swift.
@roopeshchander Choice between compiler help with safety and avoiding extra indentation.
@roopeshchander That's discussed in the comments.
@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.
@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.
@felix_schwarz Good idea. I think that would work, although it requires more free disk space than I had (or a separate drive).
@roopeshchander How does that work if I'm using "string" multiple times throughout the rest of the method?