[102] Issue #102 - Feb 8, 2018

[BasThomas]

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.

[BasThomas]

https://swiftunboxed.com/lang/conditional-conformance/

[BasThomas]

197 in review: https://github.com/apple/swift-evolution/blob/master/proposals/0197-remove-where.md

[tapthaker]

@BasThomas : That was fast !!! 197 just made it to review !!!

[BasThomas]

🏎💨

[BasThomas]

https://twitter.com/dgregor79/status/956688426065018880

[tapthaker]

@BasThomas: I couldn't be active last week. Do you want me to take up the ownership of the next week's issue.

[BasThomas]

No worries at all! If you want to write the next issue, go for it! As we’re publishing every other week, it will be the issue for February 8th. Is that OK with you?

_{Sent with GitHawk}

[tapthaker]

Yes, it is fine with me.

[BasThomas]

Can you check again if you got the invite for the organisation and accept that? Then I can also assign you as an assignee to this issue :)

[tapthaker]

Haven't got the invite. Checked everywhere. Please send it again.

[BasThomas]

You really should've been invited, I think Jesse and I already tried several times. 😁 Do you not see a button at https://github.com/swiftweekly? Can you send a screenshot of that page maybe?

Otherwise check what e-mail address is your primary one on GitHub (you can check it here) and see if you got an email there.

[tapthaker]

Joined. My bad.

[jessesquires]

@tapthaker 🎉 ~~you should go ahead and generate the draft 😊 ~~

oops nevermind. bas did already

[tapthaker]

milseman is on fire with String guts

swiftlang/swift#14186

[BasThomas]

“Removing terminology” is almost always good swiftlang/swift#14227
https://twitter.com/slava_pestov/status/957720067822706688

[tapthaker]

Was thinking of mentioning about tryswift.
https://www.tryswift.co/events/2018/tokyo/en/

[tapthaker]

https://twitter.com/SwiftSummit/status/955935679288041472

[tapthaker]

https://pspdfkit.com/blog/2018/binary-frameworks-swift/

[tapthaker]

Update: I know I haven't been writing & keeping draft up-to-date. I will ensure that it is updated by EOD tomorrow

[SD10]

@tapthaker I'm not that active around here but from what I can remember the drafts were sometimes done a couple days before. You have a ton of time to collect resources until then!

[BasThomas]

Was thinking of mentioning about tryswift.
https://www.tryswift.co/events/2018/tokyo/en/

try! Swift is awesome, but I am not so sure how it would be related to the Weekly Brief. Maybe we can share some presentations that focussed on Swift.org and its project afterwards?

https://twitter.com/SwiftSummit/status/955935679288041472

This has already been mentioned in issue 101!

Update: I know I haven't been writing & keeping draft up-to-date. I will ensure that it is updated by EOD tomorrow

No worries! Looking forward to see a draft with the first things in it 😊

[alexito4]

Hi! First time here ^^
I found https://www.skilled.io/u/swiftsummit/creating-refactoring-transformations-for-swift interesting. Would be nice to help get more attraction to the refactoring tools 👍

[BasThomas]

Hi @alexito4 👋, thanks!

_{Sent with GitHawk}

[RomanVolkov]

[Proposal] Replace PlaygroundQuickLook/CustomPlaygroundQuickLookable with new API: swiftlang/swift-evolution#784

[BasThomas]

https://twitter.com/pointfreeco/status/958103863428632576 + https://twitter.com/pointfreeco/status/958103866289086467

[BasThomas]

195 review extended swiftlang/swift-evolution@f1ef599

[gregheo]

SE-0196 approved w/ revision
https://forums.swift.org/t/se-0196-compiler-diagnostic-directives/8734/47

[BasThomas]

https://twitter.com/dgregor79/status/959213417964781568

[BasThomas]

197 accepted

[jpsim]

CountableRange removed: https://twitter.com/dgregor79/status/959466959388553216

[BasThomas]

Conditional Conformance implemented. That's a big part of ABI Stability: swiftlang/swift-evolution@3bcccee + https://twitter.com/dgregor79/status/959613002147180544

[jessesquires]

Before, we would periodically link to the proposal status page.

I think we should regularly link to this new forum page now:
https://forums.swift.org/c/evolution/proposal-reviews

With something like: "Here are the current proposals under review" and try to encourage readers to participate.

[BasThomas]

Yes, I think that would be a good idea now that it is easier than ever to do so. Also saw the tweet already - thanks!

[tapthaker]

Agreed. I will make the changes accordingly.

[BasThomas]

Awesome, thanks @tapthaker!

Let me know if I can help you with anything - we're getting closer to publishing this Thursday 😃

[BasThomas]

https://twitter.com/harlanhaskins/status/959926493190279168

[tapthaker]

@BasThomas : Thanks. I will be able to get things done on time.

[tapthaker]

I have a feeling that Bi-Weekly issues are getting long. Just worried that excessive content might overwhelm the readers. Either that or I am writing more than necessary.

[jessesquires]

@tapthaker If that's the case, we should trim to only the most important things 😊 We can help / discuss on the PR.

[RomanVolkov]

I agree with both of you @jessesquires @tapthaker It's a great idea to focus only on major news.
but the situation can be with outdated news. E.g., something important happens after new issue and it will take 2 weeks to get informed.
@jessesquires @BasThomas is it a problem from your perspective or not?

[BasThomas]

I think for those cases (which I feel are quite rare - please let me / us know if you have any!) we can send a separate tweet.

If it does turn out that the biweekly schedule doesn’t work, we can look into solving it in some way at that point.

_{Sent with GitHawk}

[modocache]

Shameless plug: is it too late to include a link to https://modocache.io/the-swift-frontend-lexing-and-parsing ?

[tapthaker]

@modocache : Thanks. I will be able to this for sure.
Just need someone up to review its @BasThomas ?

[BasThomas]

Go ahead :)

[jessesquires]

Hey @tapthaker -- not sure what happened with your intro comments on the PR. Sorry about that 😊 If you had some changes locally that you forgot to push, please open a new PR to add them 😄

[tapthaker]

git push failed for some reason but i didn't notice it. Creating a new PR

[tapthaker]

@BasThomas @jessesquires: Just added @modocache's article in the PR. Don't want to change intro comments now that it is out.