Swiftweekly.github.io: [85] Issue #85 - August 31, 2017

[jessesquires]

To contribute to this issue, simply leave a comment here. Please also review our contributing guidelines.

The current draft for this issue in _drafts/. If you want to contribute directly, open a pull request.

[jessesquires]

Hey all -- I'm going to skip this week. If someone wants to fill-in, let me know!

cc @SwiftWeekly/writers

[RomanVolkov]

@jessesquires I could

[jessesquires]

@RomanVolkov sounds good 👍 🎉

but no pressure! 😄 I likely won't be able to help much this issue with finding content.

[RomanVolkov]

@jessesquires okay) I'll manage this issue👌, but be very helpful if you'll take a rough look on result issue before merging

[BasThomas]

You can ping me if you want me to take a look as well. Will do so anyway when I find some time :)

[RomanVolkov]

@BasThomas thanks, I'll👌

[jessesquires]

https://github.com/apple/swift/pull/11613

[modocache]

As pointed out by https://twitter.com/tonyarnold/status/902377663775481856, the https://bugs.swift.org/browse/SR-5198 bug report appears to the culmination of a lot of frustration from Swift users around diagnostics and error messages for type-inferred closures.

[jessesquires]

A bit aggressive. 😞

[BasThomas]

I think that one has been discussed before - the bug was created in June.

[BasThomas]

Finally.

[RomanVolkov]

@SwiftWeekly/writers please, take a look on PR: #304
Feel free to write your suggestions and thoughts.

[jessesquires]

Thanks @RomanVolkov !