Cleanup and fix missing links. (SwiftWeekly#672)

ZevEisenberg · web-flow · commit ac0341f3fdcd · 2021-08-12T21:34:58.000+02:00
diff --git a/_posts/2021-08-12-issue-191.md b/_posts/2021-08-12-issue-191.md
@@ -67,9 +67,9 @@ Swift on the Server Workgroup meeting notes:
 > 
 > Having a standard endpoint for publishing a new release to a package registry would empower maintainers to distribute their software and promote interoperability across service providers.
 
-[Nicholas Maccharoli](https://forums.swift.org/u/nicholas_maccharoli) [purposed](https://forums.swift.org/t/if-guard-shorthand-for-optional-unwrapping/51088) a shordhand solution for optional unwrapping.
+[Nicholas Maccharoli](https://forums.swift.org/u/nicholas_maccharoli) [proposed](https://forums.swift.org/t/if-guard-shorthand-for-optional-unwrapping/51088) a shordhand solution for optional unwrapping.
 
-[Vihan Bhargava](https://twitter.com/vihanbh) wrote an aweseome overview of the new `SortedDictionary` and `SortedSet` APIs bring brought to swift-collections.
+[Vihan Bhargava](https://forums.swift.org/u/vihan) wrote an [aweseome overview](https://forums.swift.org/t/api-review-sorted-collections/51109) of the new `SortedDictionary` and `SortedSet` APIs in swift-collections.
 
 > The Swift Collections package currently includes two data structures which maintain its members in a well-defined order: `OrderedSet` and `OrderedDictionary`. These types are useful in a variety of use-cases, as they enumerate their elements in insertion order. However, there also exist many situations where its desired to maintain elements in an order specified by a predefined comparator. For example, a common pattern in user interfaces is displaying a list with entries sorted in some order, such as in chronological order.
 >
@@ -79,7 +79,7 @@ Swift on the Server Workgroup meeting notes:
 
 > C has special rules for pointer aliasing, for example allowing `char *` to alias other pointer types, and allowing pointers to signed and unsigned types to alias. The usability of some C APIs relies on the ability to easily cast pointers within the boundaries of those rules. Swift generally disallows typed pointer conversion. See [SE-0107 UnsafeRawPointer API](https://github.com/apple/swift-evolution/blob/main/proposals/0107-unsaferawpointer.md). Teaching the Swift compiler to allow pointer conversion within the rules of C when invoking functions imported from C headers will dramatically improve interoperability with no negative impact on type safety.
 
-[Brennan Stehling](https://forums.swift.org/u/brennanmke) purposed to add the throw coalescing operator to the Swift language.
+[Brennan Stehling](https://forums.swift.org/u/brennanmke) [proposed to add](https://forums.swift.org/t/throw-coalescing-operator/51137) the throw coalescing operator to the Swift language.
 
 > I'd really like syntax for `do`/`try`/`catch` which is as compact as `nil` coalescing in Swift. And so I put together a working implementation which I'd like to refine further. So far I have `!!` defined as my operator much like `??` for `nil` coalescing so it is familiar. The left operand would the work while the right would handle the error.
 

Original file line number	Diff line number	Diff line change
`@@ -67,9 +67,9 @@ Swift on the Server Workgroup meeting notes:`
`67`	`67`	`>`
`68`	`68`	`> Having a standard endpoint for publishing a new release to a package registry would empower maintainers to distribute their software and promote interoperability across service providers.`
`69`	`69`
`70`		`-[Nicholas Maccharoli](https://forums.swift.org/u/nicholas_maccharoli) [purposed](https://forums.swift.org/t/if-guard-shorthand-for-optional-unwrapping/51088) a shordhand solution for optional unwrapping.`
	`70`	`+[Nicholas Maccharoli](https://forums.swift.org/u/nicholas_maccharoli) [proposed](https://forums.swift.org/t/if-guard-shorthand-for-optional-unwrapping/51088) a shordhand solution for optional unwrapping.`
`71`	`71`
`72`		-[Vihan Bhargava](https://twitter.com/vihanbh) wrote an aweseome overview of the new `SortedDictionary` and `SortedSet` APIs bring brought to swift-collections.
	`72`	+[Vihan Bhargava](https://forums.swift.org/u/vihan) wrote an [aweseome overview](https://forums.swift.org/t/api-review-sorted-collections/51109) of the new `SortedDictionary` and `SortedSet` APIs in swift-collections.
`73`	`73`
`74`	`74`	> The Swift Collections package currently includes two data structures which maintain its members in a well-defined order: `OrderedSet` and `OrderedDictionary`. These types are useful in a variety of use-cases, as they enumerate their elements in insertion order. However, there also exist many situations where its desired to maintain elements in an order specified by a predefined comparator. For example, a common pattern in user interfaces is displaying a list with entries sorted in some order, such as in chronological order.
`75`	`75`	`>`
`@@ -79,7 +79,7 @@ Swift on the Server Workgroup meeting notes:`
`79`	`79`
`80`	`80`	> C has special rules for pointer aliasing, for example allowing `char *` to alias other pointer types, and allowing pointers to signed and unsigned types to alias. The usability of some C APIs relies on the ability to easily cast pointers within the boundaries of those rules. Swift generally disallows typed pointer conversion. See [SE-0107 UnsafeRawPointer API](https://github.com/apple/swift-evolution/blob/main/proposals/0107-unsaferawpointer.md). Teaching the Swift compiler to allow pointer conversion within the rules of C when invoking functions imported from C headers will dramatically improve interoperability with no negative impact on type safety.
`81`	`81`
`82`		`-[Brennan Stehling](https://forums.swift.org/u/brennanmke) purposed to add the throw coalescing operator to the Swift language.`
	`82`	`+[Brennan Stehling](https://forums.swift.org/u/brennanmke) [proposed to add](https://forums.swift.org/t/throw-coalescing-operator/51137) the throw coalescing operator to the Swift language.`
`83`	`83`
`84`	`84`	> I'd really like syntax for `do`/`try`/`catch` which is as compact as `nil` coalescing in Swift. And so I put together a working implementation which I'd like to refine further. So far I have `!!` defined as my operator much like `??` for `nil` coalescing so it is familiar. The left operand would the work while the right would handle the error.
`85`	`85`