Michael Tsai on Twitter: "@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."

Country	Code	For customers of
United States	40404	(any)
Canada	21212	(any)
United Kingdom	86444	Vodafone, Orange, 3, O2
Brazil	40404	Nextel, TIM
Haiti	40404	Digicel, Voila
Ireland	51210	Vodafone, O2
India	53000	Bharti Airtel, Videocon, Reliance
Indonesia	89887	AXIS, 3, Telkomsel, Indosat, XL Axiata
Italy	4880804	Wind
3424486444	Vodafone
» See SMS short codes for other countries

Roopesh Chander ‏@roopeshchander 17 Jul 2014

@mjtsai On your latest blog post, the recommended replacement for macros is functions, so: MJT_ENSURE(string, e, error)?.doSomething()
Michael Tsai ‏@mjtsai 17 Jul 2014

@roopeshchander How does that work if I'm using "string" multiple times throughout the rest of the method?
Roopesh Chander ‏@roopeshchander 17 Jul 2014

@mjtsai It doesn't :). You will have to use an `if` block in that case, I admit.
Roopesh Chander ‏@roopeshchander 17 Jul 2014

@mjtsai A minor defence: A macro with a return in it makes the code somewhat hard to read and decipher by others
Michael Tsai ‏@mjtsai 17 Jul 2014

@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.
Roopesh Chander ‏@roopeshchander 17 Jul 2014

@mjtsai I can see the value in macros like that. But I don't see a way to do that in Swift. Or rather, that doesn't fit with The Swift Way.

‏@mjtsai

@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.

6:23 AM - 17 Jul 2014

Michael TsaiVerified account