Skip to content
This repository has been archived by the owner on Mar 26, 2023. It is now read-only.

[67] Issue #67 - April 27, 2017 #224

Closed
BasThomas opened this issue Apr 20, 2017 · 18 comments
Closed

[67] Issue #67 - April 27, 2017 #224

BasThomas opened this issue Apr 20, 2017 · 18 comments
Assignees

Comments

@BasThomas
Copy link
Contributor

No description provided.

@BasThomas BasThomas self-assigned this Apr 20, 2017
BasThomas added a commit that referenced this issue Apr 20, 2017
BasThomas added a commit that referenced this issue Apr 20, 2017
@jessesquires
Copy link
Member

@BasThomas thanks so much for doing all the GH issue maintenance! 🙌

@BasThomas
Copy link
Contributor Author

You're welcome. 😃

@BasThomas
Copy link
Contributor Author

BasThomas commented Apr 20, 2017

SE-0165 accepted

@BasThomas
Copy link
Contributor Author

SE-0155 accepted

@gregheo
Copy link
Member

gregheo commented Apr 21, 2017

Couple of interesting pre-proposal pitches from Apple folks on the mailing lists:

"Should we just always import C/ObjC types under their Swift 4 names, and use typealiases in Swift 3 mode?" — dealing with renamed types when mixing and matching Swift 3/4 code.
https://lists.swift.org/pipermail/swift-dev/Week-of-Mon-20170417/004408.html

Replacing the swap function with something that follows the ownership manifesto when dealing with mutable collections.
https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170417/035986.html

@jessesquires
Copy link
Member

swift server group notes:
swift-server/work-group#80

@jessesquires
Copy link
Member

jessesquires commented Apr 22, 2017

Code size reduction:
swiftlang/swift#8909

@jessesquires
Copy link
Member

SE-0168 implementation
swiftlang/swift#8813

@BasThomas
Copy link
Contributor Author

https://twitter.com/slava_pestov/status/856367181898039296

@BasThomas
Copy link
Contributor Author

https://twitter.com/slava_pestov/status/856369805648998400

@jessesquires
Copy link
Member

Swift unwrapped 😊

https://spec.fm/podcasts/swift-unwrapped/66634

@gregheo
Copy link
Member

gregheo commented Apr 24, 2017

Source compatibility is a strong goal for future Swift releases. To aid in this goal, a community owned source compatibility test suite serves to regression test changes to the compiler against a (gradually increasing) corpus of Swift source code. Projects added to this test suite are periodically built against the latest development versions of Swift as part of Swift's continuous integration system, allowing Swift compiler developers to understand the compatibility impact their changes have on real-world Swift projects.

announcement: https://swift.org/blog/swift-source-compatibility-test-suite/

repo: https://github.com/apple/swift-source-compat-suite

tweet: https://twitter.com/tkremenek/status/856629269828575232

@BasThomas
Copy link
Contributor Author

SE-0172 accepted, SE-0171 accepted, SE-0173 in review

@jessesquires
Copy link
Member

@gregheo
Copy link
Member

gregheo commented Apr 26, 2017

"Multi-line string literals are in!"
https://twitter.com/Ilseman/status/857042195961978880

And a starter task: SR-4701 Starter: better diagnostics for multi-line string literals
https://bugs.swift.org/browse/SR-4701

@gregheo
Copy link
Member

gregheo commented Apr 26, 2017

SE-0167 accepted
https://lists.swift.org/pipermail/swift-evolution-announce/2017-April/000368.html
https://github.com/apple/swift-evolution/blob/master/proposals/0167-swift-encoders.md

@jessesquires
Copy link
Member

proposal to change SPM pinning:

https://twitter.com/rballard/status/857392666660683777
https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170424/036203.html

@BasThomas
Copy link
Contributor Author

https://twitter.com/slava_pestov/status/857457182803021824

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

3 participants