{"id":12100,"date":"2015-08-27T14:41:29","date_gmt":"2015-08-27T18:41:29","guid":{"rendered":"http:\/\/mjtsai.com\/blog\/?p=12100"},"modified":"2015-08-27T17:55:25","modified_gmt":"2015-08-27T21:55:25","slug":"swift-2-beta-6","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2015\/08\/27\/swift-2-beta-6\/","title":{"rendered":"Swift 2 Beta 6"},"content":{"rendered":"

Russ Bishop<\/a>:<\/p>\n

\n

A new try?<\/code> keyword has been added. This attempts an operation that may throw (fail). If it succeeds the result is wrapped in an optional. If it fails the error is ignored and nil<\/code> is returned. This seems like a pragmatic compromise but I have to imagine someone lost a battle somewhere because a lot of programmers are going to slap a try?<\/code> on it and ignore all errors.<\/p>\n<\/blockquote>\n

This is a good addition that was suggested<\/a> last month. I’m not worried about errors being ignored because the compiler warns if the result of try?<\/code> is unused. It lets you ignore<\/a> the specific error that you got, but you still have to handle the fact that there was an error.<\/p>\n

\n

Variadic parameters can appear anywhere in the parameter list; presumably the compiler disambiguates them by type and\/or by consuming values off the right-hand side of argument list until the non-variadic arguments are satisfied.<\/p>\n<\/blockquote>\n

It looks to me like it’s simpler than that, and you simply use a named parameter to signal the end of the variadic parameter. Perhaps in the future it will be possible to support multiple variadic parameters in this way. For now, the main benefit is that you can more easily use trailing closures.<\/p>\n

\n

extend<\/code> was renamed appendContentsOf<\/code> and splice<\/code> was renamed insertContentsOf<\/code><\/p>\n<\/blockquote>\n

It’s good to see Apple keeping some of Foundation’s good ideas.<\/p>\n

\n

Most APIs that take closures or @autoclosure<\/code> parameters use rethrows<\/code> properly so you can pass throwing methods to map<\/code>, filter<\/code>, etc. It also allows short-circuiting operators like &&<\/code>, ||<\/code>, or ??<\/code> to work with expressions that throw.<\/p>\n<\/blockquote>\n

This should make error handling easier than before<\/a>.<\/p>\n

There are still some bugs, though:<\/p>\n

\n

Declaring multiple globals in a single var<\/code> or let<\/code> may cause corruption of their values; the workaround is to declare them with separate var<\/code> or let<\/code> statements.<\/p>\n<\/blockquote>\n

Erica Sadun<\/a>:<\/p>\n

You can combine try?<\/code> with ??<\/code> for fallback values but you must surround the try in parens[…]<\/p><\/blockquote>\n

Erica Sadun<\/a>:<\/p>\n

Beta 6 introduces a lazy<\/code> property on sequences.<\/p>

[…]<\/p>

This property is implemented in CollectionType<\/code>, LazyCollectionType<\/code>, and LazySequenceType<\/code> extensions. You use it to delay evaluation on things like map and filter that are normally eager.<\/p><\/blockquote>\n

Erica Sadun<\/a>:<\/p>\n

Join<\/code> has become joinWithSeparator<\/code>, which you call after a sequence, interposing a separator between the elements of a sequence.<\/p><\/blockquote>","protected":false},"excerpt":{"rendered":"

Russ Bishop: A new try? keyword has been added. This attempts an operation that may throw (fail). If it succeeds the result is wrapped in an optional. If it fails the error is ignored and nil is returned. This seems like a pragmatic compromise but I have to imagine someone lost a battle somewhere because […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"apple_news_api_created_at":"","apple_news_api_id":"","apple_news_api_modified_at":"","apple_news_api_revision":"","apple_news_api_share_url":"","apple_news_coverimage":0,"apple_news_coverimage_caption":"","apple_news_is_hidden":false,"apple_news_is_paid":false,"apple_news_is_preview":false,"apple_news_is_sponsored":false,"apple_news_maturity_rating":"","apple_news_metadata":"\"\"","apple_news_pullquote":"","apple_news_pullquote_position":"","apple_news_slug":"","apple_news_sections":"\"\"","apple_news_suppress_video_url":false,"apple_news_use_image_component":false,"footnotes":""},"categories":[4],"tags":[46,857,71,901],"class_list":["post-12100","post","type-post","status-publish","format-standard","hentry","category-programming-category","tag-languagedesign","tag-nserror","tag-programming","tag-swift-programming-language"],"apple_news_notices":[],"_links":{"self":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts\/12100","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/comments?post=12100"}],"version-history":[{"count":2,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts\/12100\/revisions"}],"predecessor-version":[{"id":12111,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts\/12100\/revisions\/12111"}],"wp:attachment":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/media?parent=12100"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/categories?post=12100"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/tags?post=12100"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}