Update several pages with new domain name.

jeroenleenarts · jeroenleenarts · commit 7cfbaf7090bb · 2021-03-13T13:52:17.000+01:00
diff --git a/README.md b/README.md
@@ -14,7 +14,7 @@ Lovingly built with [Jekyll](https://jekyllrb.com), [Bootstrap](https://getboots
 
 ## Authors
 
-There are a number of [contributing authors](https://swiftweekly.github.io/authors/) to the newsletter. If you'd like to join, open an issue to discuss!
+There are a number of [contributing authors](https://swiftweeklybrief.com/authors/) to the newsletter. If you'd like to join, open an issue to discuss!
 
 ## Usage
 
diff --git a/_includes/search_box.html b/_includes/search_box.html
@@ -10,7 +10,7 @@
             <div class="form-group">
                 <div class="input-group">
                     <input type="search" class="form-control" placeholder="DuckDuckGo" name="q">
-                    <input type="hidden" value="swiftweekly.github.io" name="sites">
+                    <input type="hidden" value="swiftweeklybrief.com" name="sites">
                     <input type="hidden" value="1" name="kh">
                     <input type="hidden" value="1" name="kn">
                     <input type="hidden" value="1" name="kac">
diff --git a/_posts/2017-06-15-issue-74.md b/_posts/2017-06-15-issue-74.md
@@ -75,7 +75,7 @@ Chris Lattner [responded to an ongoing thread](https://lists.swift.org/pipermail
 >
 > ?
 
-We covered this back in [issue #72](https://swiftweekly.github.io/issue-72/). In Swift 4, N-ary tuples are no longer expanded to N arguments in a closure (the “tuple splat behavior”). This means closures will receive a single tuple parameter and you’ll have to expand them manually. This has (obviously) proved to be much less ergonomic and poorer developer experience. It's nice to see the Core Team reconsider this change! And who said swift-evolution wasn't great? 😉
+We covered this back in [issue #72](https://swiftweeklybrief.com/issue-72/). In Swift 4, N-ary tuples are no longer expanded to N arguments in a closure (the “tuple splat behavior”). This means closures will receive a single tuple parameter and you’ll have to expand them manually. This has (obviously) proved to be much less ergonomic and poorer developer experience. It's nice to see the Core Team reconsider this change! And who said swift-evolution wasn't great? 😉
 
 ### Finally
 
diff --git a/_posts/2017-07-06-issue-77.md b/_posts/2017-07-06-issue-77.md
@@ -9,7 +9,7 @@ sponsor:
     displaylink: buddybuild.com
 ---
 
-After some time off and a break from the weekly, I'm back! Before we get started, I'd like to send a final massive thanks to the other [Swift Weekly writers and contributors](https://swiftweekly.github.io/authors/) for doing such a great job the past few weeks. This team is great and they worked super hard to bring you the best Swift news, and even helped with this issue. Alright &mdash; let's get to it!
+After some time off and a break from the weekly, I'm back! Before we get started, I'd like to send a final massive thanks to the other [Swift Weekly writers and contributors](https://swiftweeklybrief.com/authors/) for doing such a great job the past few weeks. This team is great and they worked super hard to bring you the best Swift news, and even helped with this issue. Alright &mdash; let's get to it!
 
 <!--excerpt-->
 
diff --git a/_posts/2017-08-10-issue-82.md b/_posts/2017-08-10-issue-82.md
@@ -49,7 +49,7 @@ From [Slava Pestov](https://twitter.com/slava_pestov/status/895097488079634433)
 
 Roman Levenstein [merged](https://github.com/apple/swift/pull/11380) changes to reduce the stdlib size by 200KB.
 
-Back in [Issue #71](https://swiftweekly.github.io/issue-71/), we covered George Karpenkov's [pull request](https://github.com/apple/swift/pull/9450) to add support for the `-sanitize=fuzzer flag`. This was finally merged this week.
+Back in [Issue #71](https://swiftweeklybrief.com/issue-71/), we covered George Karpenkov's [pull request](https://github.com/apple/swift/pull/9450) to add support for the `-sanitize=fuzzer flag`. This was finally merged this week.
 
 Michael Ilseman opened a [pull request](https://github.com/apple/swift/pull/11373) to change `String.CharacterView` from being its own slice type to use `Substring.CharacterView` instead, as well as making it `RangeReplaceable`. *"This aligns with the goal of introducing Substring as a separate type
 to avoid accidental memory 'leaks'."* The PR also removes some old Unicode 8 code.
diff --git a/_posts/2017-11-30-issue-96.md b/_posts/2017-11-30-issue-96.md
@@ -4,7 +4,7 @@ title: ! 'Issue #96'
 author: jsq
 ---
 
-I've returned! 😊 Welcome back to the weekly. We skipped last week and I haven't written the last few issues, but luckily we have [some amazing contributors](https://swiftweekly.github.io/authors/) to help bring this to your inbox each week. Big thanks to [Bas](https://twitter.com/basthomas), [Brian](https://twitter.com/modocache), and [Roman](https://twitter.com/volkovre). I was traveling and speaking at [iOS Conf Singapore](http://iosconf.sg) and then the very first [try! Swift India](https://www.tryswift.co/events/2017/bangalore/) &mdash; both of which were great!
+I've returned! 😊 Welcome back to the weekly. We skipped last week and I haven't written the last few issues, but luckily we have [some amazing contributors](https://swiftweeklybrief.com/authors/) to help bring this to your inbox each week. Big thanks to [Bas](https://twitter.com/basthomas), [Brian](https://twitter.com/modocache), and [Roman](https://twitter.com/volkovre). I was traveling and speaking at [iOS Conf Singapore](http://iosconf.sg) and then the very first [try! Swift India](https://www.tryswift.co/events/2017/bangalore/) &mdash; both of which were great!
 
 This week, we saw a progress on conditional conformances, a few new proposals, and discussions on Swift interop with Python.
 
diff --git a/_posts/2017-12-21-issue-99.md b/_posts/2017-12-21-issue-99.md
@@ -4,7 +4,7 @@ title: ! 'Issue #99'
 author: jsq
 ---
 
-Welcome to issue #99! 🎈 [Last week we discussed](https://swiftweekly.github.io/issue-98/) the move away from the mailing lists to official Swift forums, which were intended to be fully rolled out by now. Unfortunately, the rollout has been delayed until early next year due to feedback from users and the holiday season. Almost there! In other news, two exciting proposals were introduced this week that have significant implications for library authors, the Swift ABI, and potential performance improvements. Swift 5 is starting to look like a very exciting release!
+Welcome to issue #99! 🎈 [Last week we discussed](https://swiftweeklybrief.com/issue-98/) the move away from the mailing lists to official Swift forums, which were intended to be fully rolled out by now. Unfortunately, the rollout has been delayed until early next year due to feedback from users and the holiday season. Almost there! In other news, two exciting proposals were introduced this week that have significant implications for library authors, the Swift ABI, and potential performance improvements. Swift 5 is starting to look like a very exciting release!
 
 <!--excerpt-->
 
diff --git a/_posts/2018-01-04-issue-100.md b/_posts/2018-01-04-issue-100.md
@@ -72,6 +72,6 @@ case bar:
 
 ### Finally
 
-And finally &mdash; thank you for reading. I cannot say 'thank you' enough. Thanks for reading these issues over the past two years. Thanks to all of the fantastic sponsors that helped motivate and incentivize me to keep writing. And thanks to [the other great writers](https://swiftweekly.github.io/authors/) who wrote issues so that I could take much-needed breaks: [Brian Gesiak](https://twitter.com/modocache), [JP Simard](https://twitter.com/simjp), [Bas Broek](https://twitter.com/BasThomas), [Greg Heo](https://twitter.com/gregheo), [Ben Asher](https://twitter.com/benasher44), [Garric Nahapetian](https://twitter.com/garricn), and [Roman Volkov](https://twitter.com/volkovre).
+And finally &mdash; thank you for reading. I cannot say 'thank you' enough. Thanks for reading these issues over the past two years. Thanks to all of the fantastic sponsors that helped motivate and incentivize me to keep writing. And thanks to [the other great writers](https://swiftweeklybrief.com/authors/) who wrote issues so that I could take much-needed breaks: [Brian Gesiak](https://twitter.com/modocache), [JP Simard](https://twitter.com/simjp), [Bas Broek](https://twitter.com/BasThomas), [Greg Heo](https://twitter.com/gregheo), [Ben Asher](https://twitter.com/benasher44), [Garric Nahapetian](https://twitter.com/garricn), and [Roman Volkov](https://twitter.com/volkovre).
 
 This is the final "finally", at least for awhile. Until next time. <br/>&mdash;jsq
diff --git a/_posts/2018-01-25-issue-101.md b/_posts/2018-01-25-issue-101.md
@@ -7,7 +7,7 @@ author: btb
 Hi! 👋
 
 [We're back](https://basthomas.github.io/curating-swift-weekly). After a short hiatus, we are continuing Swift Weekly Brief every other week. 🎉
-As Jesse [mentioned](https://www.jessesquires.com/blog/swift-weekly-brief-hiatus/), he will be taking a break from writing the newsletter. I will be taking over the curation of the newsletter for now, with the help of some awesome [contributors](https://github.com/SwiftWeekly/swiftweekly.github.io/graphs/contributors) and [writers](https://swiftweekly.github.io/authors/).
+As Jesse [mentioned](https://www.jessesquires.com/blog/swift-weekly-brief-hiatus/), he will be taking a break from writing the newsletter. I will be taking over the curation of the newsletter for now, with the help of some awesome [contributors](https://github.com/SwiftWeekly/swiftweekly.github.io/graphs/contributors) and [writers](https://swiftweeklybrief.com/authors/).
 
 There is more great news: the [Swift Forums](https://forums.swift.org/t/welcome-to-the-swift-forums/8) are now live! They offer a more visual, searchable and navigatable way of browsing through the previous mailing lists. This will hopefully make the barrier for chiming in on everything Swift.org lower. Go [have a look](https://forums.swift.org) - and a huge congratulations to the team at Apple for realising this.
 
diff --git a/_posts/2018-10-04-issue-119.md b/_posts/2018-10-04-issue-119.md
@@ -9,7 +9,7 @@ sponsor:
     displaylink: do-ios.com
 ---
 
-We're very happy to re-introduce the newsletter's mail subscriptions, so that you can once again receive Swift Weekly Brief in your inbox. If you haven't yet and are interested, you can subscribe [here](https://swiftweekly.github.io/subscribe/).
+We're very happy to re-introduce the newsletter's mail subscriptions, so that you can once again receive Swift Weekly Brief in your inbox. If you haven't yet and are interested, you can subscribe [here](https://swiftweeklybrief.com/subscribe/).
 
 Enjoy the newsletter and have a great weekend and week!
 
diff --git a/_posts/2020-05-21-issue-160.md b/_posts/2020-05-21-issue-160.md
@@ -20,7 +20,7 @@ After all, I took over the curation of this newsletter from Jesse because I
 wanted to keep sharing what's happening in Swift open source with all those
 others benefiting from it.
 
-There are also still [sponsorship opportunities](https://swiftweekly.github.io/sponsorship/)
+There are also still [sponsorship opportunities](https://swiftweeklybrief.com/sponsorship/)
 for the newsletter, and I would greatly appreciate it if you could share that
 with those who might be interested in helping with the newsletter in that way.
 It allows us to keep delivering it to your inbox every other Thursday!
diff --git a/_posts/2020-10-22-issue-171.md b/_posts/2020-10-22-issue-171.md
@@ -6,7 +6,7 @@ author: fassko
 
 The last two weeks were somewhat slow in the Swift open source world but then Apple published yet another open-source library - [Swift Service Discovery](https://github.com/apple/swift-service-discovery). Apart from the announcement of the new iPhones we had some weird times with Xcode 12.1 and 12.2 beta 3 🤔.
 
-To continue sending out this newsletter to your emails, we are looking for sponsors to cover the cost of the platform we are using. More info about that can be found [here](https://swiftweekly.github.io/sponsorship/). Or you can reach out to me personally on Twitter [@fassko](https://twitter.com/fassko). Thanks! 🙏
+To continue sending out this newsletter to your emails, we are looking for sponsors to cover the cost of the platform we are using. More info about that can be found [here](https://swiftweeklybrief.com/sponsorship/). Or you can reach out to me personally on Twitter [@fassko](https://twitter.com/fassko). Thanks! 🙏
 
 <!--excerpt-->
 
diff --git a/_posts/2021-03-11-issue-180.md b/_posts/2021-03-11-issue-180.md
@@ -13,7 +13,7 @@ Another two weeks have passed in the blink of an eye. I've been busy launching m
 
 [Jeroen Leenarts](https://twitter.com/AppForce1) and I teamed up to improve the mailing list platform we're using to send out this newsletter, and hopefully to cut costs. This week is the first real test. If this email finds your mailbox, then we know it's working. :)
 
-I want to thank all the supporters, sponsors and everyone in the Swift community who help make this project happen. If you have any ideas about things to change, improve upon, or help [support this newsletter financially](https://swiftweekly.github.io/sponsorship/), please [let me know](mailto:fassko@gmail.com).
+I want to thank all the supporters, sponsors and everyone in the Swift community who help make this project happen. If you have any ideas about things to change, improve upon, or help [support this newsletter financially](https://swiftweeklybrief.com/sponsorship/), please [let me know](mailto:fassko@gmail.com).
 
 Without further ado, we have some great news this time!
 

Original file line number	Diff line number	Diff line change
`@@ -75,7 +75,7 @@ Chris Lattner [responded to an ongoing thread](https://lists.swift.org/pipermail`
`75`	`75`	`>`
`76`	`76`	`> ?`
`77`	`77`
`78`		`-We covered this back in [issue #72](https://swiftweekly.github.io/issue-72/). In Swift 4, N-ary tuples are no longer expanded to N arguments in a closure (the “tuple splat behavior”). This means closures will receive a single tuple parameter and you’ll have to expand them manually. This has (obviously) proved to be much less ergonomic and poorer developer experience. It's nice to see the Core Team reconsider this change! And who said swift-evolution wasn't great? 😉`
	`78`	`+We covered this back in [issue #72](https://swiftweeklybrief.com/issue-72/). In Swift 4, N-ary tuples are no longer expanded to N arguments in a closure (the “tuple splat behavior”). This means closures will receive a single tuple parameter and you’ll have to expand them manually. This has (obviously) proved to be much less ergonomic and poorer developer experience. It's nice to see the Core Team reconsider this change! And who said swift-evolution wasn't great? 😉`
`79`	`79`
`80`	`80`	`### Finally`
`81`	`81`