[swift-evolution] [META] Gmane and Swift Evolution

Tue Aug 2 10:16:26 CDT 2016

On Aug 1, 2016, at 12:46 PM, Krishna Kumar <kkdevenda at gmail.com> wrote:
> 
> Hey
> 
> I’ll update (SE0017 - SE0045)
> 
> Thanks
> 
> -Krishna

Thanks.

Remaining links as of this morning are listed below. Anyone willing to adopt a proposal or a group and get them updated, please reply in-thread and submit a PR with changes.

Tips: 

* Ideally, each proposal should have a link to a rationale, to on-list discussion(s), and review discussion(s). If any of these are missing, please add.
* Rationales are easily found on the announcement list: https://lists.swift.org/pipermail/swift-evolution-announce/ <https://lists.swift.org/pipermail/swift-evolution-announce/>
* Discussion and review threads need to be from the non-announce list to allow readers to follow the conversation.
* A few proposals are sourced from build-dev and not Swift Evolution
* The toughest updates were from December, before the archiving, formatting, etc got underway. Later links are a lot easier to track down.
* You cannot use Google to search for gmane threads as the site was set for no robots and there is no Internet Archive Wayback fallback. 

-- E

proposals/0030-property-behavior-decls.md:* Status: **Rejected** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/7735))
proposals/0030-property-behavior-decls.md:[Swift Evolution Discussion](http://thread.gmane.org/gmane.comp.lang.swift.evolution/11976)<br/>
proposals/0030-property-behavior-decls.md:[Review](http://thread.gmane.org/gmane.comp.lang.swift.evolution/6426)
proposals/0031-adjusting-inout-declarations.md:* Status: **Accepted for Swift 3** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/7394))
proposals/0031-adjusting-inout-declarations.md:*The initial Swift-Evolution discussion of this topic took place in the "[Replace 'inout' with &](http://comments.gmane.org/gmane.comp.lang.swift.evolution/2751)" thread.*
proposals/0032-sequencetype-find.md:* Status: **Accepted for Swift 3** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/16116))
proposals/0033-import-objc-constants.md:* Status: **Implemented in Swift 3** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/8817))
proposals/0034-disambiguating-line.md:* Status: **Accepted** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/8156), [Implementation Bug](https://bugs.swift.org/browse/SR-840))
proposals/0034-disambiguating-line.md:The discussion took place on-line in the [*\[Discussion\]: Renaming #line, the line control statement*](http://comments.gmane.org/gmane.comp.lang.swift.evolution/5815) thread.
proposals/0035-limit-inout-capture.md:* Status: **Accepted** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/7732), [Bug](https://bugs.swift.org/browse/SR-807))
proposals/0036-enum-dot.md:*Discussion took place on the Swift Evolution mailing list in the [\[Discussion\] Enum Leading Dot Prefixes](http://article.gmane.org/gmane.comp.lang.swift.evolution/6684) thread. This proposal uses lowerCamelCase enumeration cases in compliance with
proposals/0036-enum-dot.md:current [API Guideline Working Group guidance](http://news.gmane.org/gmane.comp.lang.swift.evolution).*
proposals/0037-clarify-comments-and-operators.md:* Status: **Accepted** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/12350), [Bug](https://bugs.swift.org/browse/SR-960))
proposals/0037-clarify-comments-and-operators.md:Swift-evolution thread: [started here](http://thread.gmane.org/gmane.comp.lang.swift.evolution/605)
proposals/0037-clarify-comments-and-operators.md:and [continued here](http://thread.gmane.org/gmane.comp.lang.swift.evolution/2855).
proposals/0038-swiftpm-c-language-targets.md:[Swift Evolution Review Thread](http://thread.gmane.org/gmane.comp.lang.swift.evolution/7293)
proposals/0039-playgroundliterals.md:* Status: **Accepted** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/9149/), [Bug](https://bugs.swift.org/browse/SR-917))
proposals/0039-playgroundliterals.md:*Discussion took place on the Swift Evolution mailing list in the [\[Discussion\] Modernizing Playground Literals](http://article.gmane.org/gmane.comp.lang.swift.evolution/7124) thread. Thanks to [Chris Lattner](https://github.com/lattner) for suggesting this enhancement.*
proposals/0045-scan-takewhile-dropwhile.md:* Status: **Accepted for Swift 3** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/16119), [Bug](https://bugs.swift.org/browse/SR-1516))
proposals/0045-scan-takewhile-dropwhile.md:[Proposal: Add scan, takeWhile, dropWhile, and iterate to the stdlib](http://thread.gmane.org/gmane.comp.lang.swift.evolution/1515)
proposals/0045-scan-takewhile-dropwhile.md:[rationale]: http://article.gmane.org/gmane.comp.lang.swift.evolution/16119
proposals/0076-copying-to-unsafe-mutable-pointer-with-unsafe-pointer-source.md:* Status: **Accepted with Revisions for Swift 3** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/16898), [Bug](https://bugs.swift.org/browse/SR-1490))
proposals/0079-upgrade-self-from-weak-to-strong.md:[Swift Evolution Discussion Thread](http://thread.gmane.org/gmane.comp.lang.swift.evolution/7582), [Draft Proposal](http://thread.gmane.org/gmane.comp.lang.swift.evolution/6064)
proposals/0080-failable-numeric-initializers.md:* Status: **Accepted with Revisions for Swift 3** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/16899), [Bug](https://bugs.swift.org/browse/SR-1491))
proposals/0081-move-where-expression.md:[\[Pitch\] Moving where Clauses Out Of Parameter Lists](http://thread.gmane.org/gmane.comp.lang.swift.evolution/13886/focus=13899)
proposals/0082-swiftpm-package-edit.md:* Status: **Accepted for Swift 3** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/16614))
proposals/0082-swiftpm-package-edit.md:[Proposal Announcement](http://thread.gmane.org/gmane.comp.lang.swift.evolution/15279)
proposals/0082-swiftpm-package-edit.md:[Review announcement](http://thread.gmane.org/gmane.comp.lang.swift.evolution/16078)
proposals/0085-package-manager-command-name.md:* Status: **Implemented in Swift 3** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.build/1/focus=26))
proposals/0085-package-manager-command-name.md:[Swift Build Review Thread](http://thread.gmane.org/gmane.comp.lang.swift.build/1/)
proposals/0085-package-manager-command-name.md:[Swift Evolution Review Thread](http://thread.gmane.org/gmane.comp.lang.swift.build/1/focus=16764)
proposals/0086-drop-foundation-ns.md:* Status: **Accepted** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/23869))
proposals/0086-drop-foundation-ns.md:[Swift Evolution Discussion Thread](http://thread.gmane.org/gmane.comp.lang.swift.evolution/16298)
proposals/0086-drop-foundation-ns.md:[Review Thread](http://thread.gmane.org/gmane.comp.lang.swift.evolution/16509)
proposals/0088-libdispatch-for-swift3.md:* Status: **Accepted with Revisions** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/17819))
proposals/0088-libdispatch-for-swift3.md:[Review thread](http://thread.gmane.org/gmane.comp.lang.swift.evolution/16745)
proposals/0092-typealiases-in-protocols.md:* Status: **Implemented in Swift 3.0** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/17317))
proposals/0094-sequence-function.md:Swift-evolution thread: [Discussion thread topic for that proposal](http://thread.gmane.org/gmane.comp.lang.swift.evolution/15743/focus=17108)
proposals/0094-sequence-function.md:[SE-0045a]: http://article.gmane.org/gmane.comp.lang.swift.evolution/16119
proposals/0095-any-as-existential.md:Discussion threads: [pre-proposal](https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160516/018109.html), [review thread 1](http://thread.gmane.org/gmane.comp.lang.swift.evolution/18349), [2](http://thread.gmane.org/gmane.comp.lang.swift.evolution/18350/focus=18447), [3](http://thread.gmane.org/gmane.comp.lang.swift.evolution/18351/focus=18440), [4](http://thread.gmane.org/gmane.comp.lang.swift.evolution/18518), [post-review thread](http://thread.gmane.org/gmane.comp.lang.swift.evolution/19463)
proposals/0096-dynamictype.md:[RFC: didset and willset](http://thread.gmane.org/gmane.comp.lang.swift.evolution/17534)
proposals/0097-negative-attributes.md:[RFC: didset and willset](http://thread.gmane.org/gmane.comp.lang.swift.evolution/17534)
proposals/0098-didset-capitalization.md:[RFC: didset and willset](http://thread.gmane.org/gmane.comp.lang.swift.evolution/17534)
proposals/0099-conditionclauses.md:[\[Pitch\] making where and ,	interchangeable in guard conditions](http://thread.gmane.org/gmane.comp.lang.swift.evolution/17926)
proposals/0101-standardizing-sizeof-naming.md:* Swift Evolution Pitch: [\[Pitch\] Renaming sizeof, sizeofValue, strideof,	strideofValue](http://thread.gmane.org/gmane.comp.lang.swift.evolution/19459)
proposals/0101-standardizing-sizeof-naming.md:* [Earlier Discussions](http://thread.gmane.org/gmane.comp.lang.swift.evolution/15830)
proposals/0101-standardizing-sizeof-naming.md:* [SE-0101 Review](http://thread.gmane.org/gmane.comp.lang.swift.evolution/21103)
proposals/0103-make-noescape-default.md:* [Make non-escaping closures the default](http://thread.gmane.org/gmane.comp.lang.swift.evolution/19756)
proposals/0105-remove-where-from-forin-loops.md:Swift Evolution Discussion: [\[Pitch\] Retiring `where` from for-in loops](http://thread.gmane.org/gmane.comp.lang.swift.evolution/20142)
proposals/0106-rename-osx-to-macos.md:Swift Evolution Discussion: [\[DRAFT\] Aliasing the OS X Platform Configuration	Test](http://thread.gmane.org/gmane.comp.lang.swift.evolution/20815)
proposals/0108-remove-assoctype-inference.md:swift-evolution thread: [pre-proposal](http://thread.gmane.org/gmane.comp.lang.swift.evolution/21714)
proposals/0108-remove-assoctype-inference.md:As Douglas Gregor (original author of the relevant type inference code) [puts it](http://article.gmane.org/gmane.comp.lang.swift.evolution/22058):
proposals/0108-remove-assoctype-inference.md:To some extent, this is an issue inherent to any design which makes no distinctions at the site of implementation between members intended to satisfy protocol requirements and members that are explicitly not intended to satisfy protocol requirements. Rather than adding keywords to create this distinction, Douglas Gregor has [proposed and implemented type checker heuristics](http://article.gmane.org/gmane.comp.lang.swift.devel/1799) that will generate warnings when a programmer implements a member that "looks like" it should fulfill a protocol requirement but does not actually do so. This is one possible mitigation strategy that should be revisited as a way to decrease the possible impact of removing associated type witness inference from the compiler.
proposals/0108-remove-assoctype-inference.md:As well, Dave Abrahams expresses a [potential issue](http://article.gmane.org/gmane.comp.lang.swift.evolution/21892):
proposals/0109-remove-boolean.md:* Status: Accepted ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/23844))
proposals/0109-remove-boolean.md:[Discussion thread](http://thread.gmane.org/gmane.comp.lang.swift.evolution/21559)
proposals/0110-distingish-single-tuple-arg.md:Discussion: [pre-proposal](http://thread.gmane.org/gmane.comp.lang.swift.evolution/21732)
proposals/0111-remove-arg-label-type-significance.md:Discussion: [pre-proposal](http://thread.gmane.org/gmane.comp.lang.swift.evolution/21369)
proposals/0114-buffer-naming.md:[Swift Evolution Thread](http://thread.gmane.org/gmane.comp.lang.swift.evolution/22127)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160802/a7029a19/attachment.html>