Swiftweekly.github.io: [102] Issue #102 - Feb 8, 2018
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
All 52 comments
BasThomas
on 25 Jan 2018
BasThomas
on 25 Jan 2018
@BasThomas : That was fast !!! 197 just made it to review !!!
tapthaker
on 25 Jan 2018
🏎💨
BasThomas
on 25 Jan 2018
BasThomas
on 26 Jan 2018
@BasThomas: I couldn't be active last week. Do you want me to take up the ownership of the next week's issue.
tapthaker
on 26 Jan 2018
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
BasThomas
on 26 Jan 2018
Yes, it is fine with me.
tapthaker
on 26 Jan 2018
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 :)
BasThomas
on 26 Jan 2018
Haven't got the invite. Checked everywhere. Please send it again.
tapthaker
on 26 Jan 2018
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.
BasThomas
on 26 Jan 2018
Joined. My bad.
tapthaker
on 26 Jan 2018
@tapthaker 🎉 ~~you should go ahead and generate the draft 😊 ~~
oops nevermind. bas did already
jessesquires
on 26 Jan 2018
milseman is on fire with String guts
tapthaker
on 26 Jan 2018
“Removing terminology” is almost always good https://github.com/apple/swift/pull/14227
https://twitter.com/slava_pestov/status/957720067822706688
BasThomas
on 28 Jan 2018
Was thinking of mentioning about tryswift.
https://www.tryswift.co/events/2018/tokyo/en/
tapthaker
on 29 Jan 2018
tapthaker
on 29 Jan 2018
tapthaker
on 29 Jan 2018
Update: I know I haven't been writing & keeping draft up-to-date. I will ensure that it is updated by EOD tomorrow
tapthaker
on 29 Jan 2018
@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!
SD10
on 29 Jan 2018
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?
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 😊
BasThomas
on 29 Jan 2018
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 👍
alexito4
on 29 Jan 2018
Hi @alexito4 👋, thanks!
Sent with GitHawk
BasThomas
on 30 Jan 2018
[Proposal] Replace PlaygroundQuickLook/CustomPlaygroundQuickLookable with new API: https://github.com/apple/swift-evolution/pull/784
RomanVolkov
on 30 Jan 2018
https://twitter.com/pointfreeco/status/958103863428632576 + https://twitter.com/pointfreeco/status/958103866289086467
BasThomas
on 30 Jan 2018
RomanVolkov
on 31 Jan 2018
Conditional conformance to Hashable
jessesquires
on 31 Jan 2018
BasThomas
on 31 Jan 2018
BasThomas
on 1 Feb 2018
198 in review https://github.com/apple/swift-evolution/pull/784
BasThomas
on 1 Feb 2018
195 review extended https://github.com/apple/swift-evolution/commit/f1ef59909b8f6bad7ba0f85152ca294d0b310638
BasThomas
on 1 Feb 2018
SE-0196 approved w/ revision
https://forums.swift.org/t/se-0196-compiler-diagnostic-directives/8734/47
gregheo
on 2 Feb 2018
BasThomas
on 2 Feb 2018
197 accepted
BasThomas
on 2 Feb 2018
CountableRange removed: https://twitter.com/dgregor79/status/959466959388553216
jpsim
on 2 Feb 2018
Conditional Conformance implemented. That's a big part of ABI Stability: https://github.com/apple/swift-evolution/commit/3bccceedbe9085c5e1a7e79d8a6cf2bfaa06d476 + https://twitter.com/dgregor79/status/959613002147180544
BasThomas
on 3 Feb 2018
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.
jessesquires
on 3 Feb 2018
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!
BasThomas
on 3 Feb 2018
Agreed. I will make the changes accordingly.
tapthaker
on 4 Feb 2018
Awesome, thanks @tapthaker!
Let me know if I can help you with anything - we're getting closer to publishing this Thursday 😃
BasThomas
on 4 Feb 2018
BasThomas
on 4 Feb 2018
@BasThomas : Thanks. I will be able to get things done on time.
tapthaker
on 4 Feb 2018
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.
tapthaker
on 5 Feb 2018
@tapthaker If that's the case, we should trim to only the most important things 😊 We can help / discuss on the PR.
jessesquires
on 5 Feb 2018
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?
RomanVolkov
on 5 Feb 2018
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
BasThomas
on 5 Feb 2018
Shameless plug: is it too late to include a link to https://modocache.io/the-swift-frontend-lexing-and-parsing ?
modocache
on 8 Feb 2018
@modocache : Thanks. I will be able to this for sure.
Just need someone up to review its @BasThomas ?
tapthaker
on 8 Feb 2018
Go ahead :)
BasThomas
on 8 Feb 2018
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 😄
jessesquires
on 8 Feb 2018
git push failed for some reason but i didn't notice it. Creating a new PR
tapthaker
on 8 Feb 2018
@BasThomas @jessesquires: Just added @modocache's article in the PR. Don't want to change intro comments now that it is out.
tapthaker
on 8 Feb 2018
Related issues
jessesquires
·
6Comments
jessesquires
·
10Comments
ColinEberhardt
·
5Comments
jessesquires
·
4Comments
jessesquires
·
8Comments
Most helpful comment
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.