"Unannotated single-expression closures with non-Void return types can now be used in Void contexts" yesss
Conversation
OK, you can explain. Why is that good?
1
You end up having to add "blank returns" all over the place if you use concise closure syntax.
1
But doesn't that ignore the return value? Isn't that usually bad? "non-void used in a void context". I haven't hit this.
3
Replying to
Happens a lot if you try to do method-chain-y things (e.g. Cartography) or use certain overzealous APIs (e.g. JavaScriptCore).