Post issue 131

Closes #448

Author: BasThomas

_drafts/2019-04-04-issue-131.md renamed to _posts/2019-04-04-issue-131.md

@@ -4,7 +4,11 @@ title: ! 'Issue #131'
 author: btb
 ---
 
-Xcode 10.2, Swift 5, Swift 5.1, _tons_ of proposals
+A busy two weeks: the long-awaiting Swift 5 was released, alongside Xcode 10.2.
+It took a while, but it is awesome to see this great release come to life.
+
+Furthermore, Swift 5.1 is already being worked on, and there are _tons_ of
+proposals ongoing, so you can expect a lot more interesting things to come!
 
 <!--excerpt-->
 
@@ -13,7 +17,8 @@ Xcode 10.2, Swift 5, Swift 5.1, _tons_ of proposals
 ### Starter tasks
 
 - [TF-360](https://bugs.swift.org/browse/TF-360) [Tests] Create unit test for `TensorFlow.h:convertSwiftTypeToTF`
-- [TF-361](https://bugs.swift.org/browse/TF-361) [Python interop] Python member lookup error gives bad error message
+- [TF-416](https://bugs.swift.org/browse/TF-416) [Python interop] Produce error upon second usage of `PythonLibrary.useVersion`
+- [TF-419](https://bugs.swift.org/browse/TF-419) Improve tensor printing
 
 ### Podcasts
 
@@ -31,11 +36,23 @@ on the Swift.org blog.
 > developers should be necessary, but it’s worth highlighting some of the
 > benefits this move gives us now and in the future.
 
+SwiftNIO 2 [has been released](https://forums.swift.org/t/swiftnio-2/22136)!
+
+Swift 5 [has been released](https://swift.org/blog/swift-5-released/)! You can
+find the release notes [here](https://developer.apple.com/documentation/xcode_release_notes/xcode_10_2_release_notes/swift_5_release_notes_for_xcode_10_2).
+
 ### Commits and pull requests
 
 [Nathan Hawes](https://github.com/nathawes) merged [a pull request](https://github.com/apple/swift/pull/23448)
 to fix variable renaming in switches.
 
+[Slava Pestov](https://twitter.com/slava_pestov) merged [a pull request](https://github.com/apple/swift/pull/23734)
+that adds support for default arguments on subscripts. 🎉
+
+[Ben Langmuir](https://twitter.com/benlangmuir) merged [a pull request](https://github.com/apple/swift/pull/23674)
+that fixes an infinite looping looking up superclasses, the same day it was
+[reported](https://bugs.swift.org/browse/SR-10236). 🏎
+
 ### Accepted proposals
 
 [SE-0252](https://github.com/apple/swift-evolution/blob/master/proposals/0252-keypath-dynamic-member-lookup.md): *Key Path Member Lookup* was [accepted](https://forums.swift.org/t/accepted-se-0252-key-path-member-lookup/22570/2).
@@ -244,6 +261,16 @@ returns from Single-Expression Functions.
 > `return` keyword can be omitted. We should provide this shorthand for
 > functions as well.
 
+[David Smith](https://twitter.com/Catfish_Man) pitched [a proposal](https://forums.swift.org/t/pitch-add-a-string-initializer-with-access-to-uninitialized-storage/22611)
+to add a `String` initializer with access to uninitialized storage.
+
+> I've been working on improving the performance of `NSString`-to-`String`
+> bridging, and Michael Ilseman pointed out that the more we can build it out
+> of public API rather than adding a bunch of private stuff for Foundation's
+> use, the better off everyone is.
+>
+> This new initializer is designed to be consistent with the [recently-accepted similar initializer on `Array`](https://github.com/apple/swift-evolution/blob/master/proposals/0245-array-uninitialized-initializer.md).
+
 [Doug Gregor](https://twitter.com/dgregor79)
 pitched [a proposal](https://forums.swift.org/t/pitch-property-delegates/21895)
 to add Property Delegates.
@@ -261,6 +288,25 @@ to add Property Delegates.
 > discusses the substantive differences from that design at the end of this
 > proposal.
 
+[Saleem Abdulrasool]() shared [an update](https://forums.swift.org/t/swift-windows/22458)
+on Swift on Windows.
+
+> I think at this point, with pending patches, we should be able to claim that
+> Windows support is as good as macOS and Linux!
+>
+> I have been working on Foundation as well, which is in a better shape than
+> before. It is possible to build it on Windows, though there is pending work
+> to refactor the build a slight bit which will improve things and enable the
+> nightlies to build Foundation as well. However, getting the library to build
+> is only the beginning and running through the test suite should help get some
+> level of confidence in the library functioning properly.
+>
+> The Windows instructions have been updated to reflect all of this
+> information, and it should be possible for others to replicate this work as
+> well. Overall, it seems that most of the compiler, runtime, and core
+> libraries are now usable on Windows with the test coverage quickly converging
+> to the point where it is nearly as good as the other supported platforms!
+
 [Brent Royal-Gordon](https://twitter.com/brentdax)
 pitched [a proposal](https://forums.swift.org/t/pitch-static-and-class-subscripts/21850)
 to allow `static` and `class` subscripts.
@@ -271,7 +317,7 @@ to allow `static` and `class` subscripts.
 > expect of a subscript. We also propose extending dynamic member lookup and
 > key paths to static properties by using static subscripts.
 
-[Michael Ilseman]() gave [an update](https://forums.swift.org/t/string-consumption/21907)
+[Michael Ilseman](https://twitter.com/ilseman) gave [an update](https://forums.swift.org/t/string-consumption/21907)
 on "`String` Consumption".
 
 > **Collection consumers**
@@ -301,4 +347,4 @@ on "`String` Consumption".
 
 ### Finally
 
-> TODO: something funny/fun. tweet, link, etc.
+Syntax [is still hard](https://twitter.com/jesse_squires/status/1113547347756064768)...