Closed BasThomas closed 5 years ago
Swift Server Workgroup meeting July 25th, 2019
Opening this thread up to continue the discussion started here, about whether it's appropriate provide a default implementation relying on
ObjectIdentifier
.To set expectations clearly: the proposal has been accepted and the default implementation will ship in Swift 5.1. There is no possibility of it being removed from that release, given the point we are at in the convergence of 5.1, regardless of the direction of this discussion.
https://forums.swift.org/t/identifiable-and-object-identity/27784
https://twitter.com/olebegemann/status/1160846803274801152
Autodiscovery of test methods on Linux* is now a thing in recent Swift 5.1 snapshots. You should be able to delete LinuxMain.swift and run your tests with:
swift test --enable-test-discovery
- and other non-Darwin platforms
[..] here’s @aciidb0mb3r’s PR: https://github.com/apple/swift-package-manager/pull/2174. Looks like it extracts the symbols from the compiled object files and generates the necessary __allTests extensions on the fly.
stdlibCore now always lowers ownership /after/ running the diagnostic passes
Early this morning, I flipped the switch causing stdlibCore to always lower ownership /after/ running the diagnostic passes. This is a large milestone for ownership in general since this is the first time we have exposed some passes downstream of the Mandatory Inlining to ownership in the build itself (vs tests). It will ensure that changes in tree do not break basic functionality when we are in this mode (something that I have run into)
https://twitter.com/Lukasaoz/status/1161323863411777537
https://forums.swift.org/t/swiftnio-http-2-security-notice/27855
All swift-nio-http2 users, please update to swift-nio-http2 version 1.5.0 urgently.
A number of HTTP/2 server implementations have been discovered to be at risk of a number of different denial of service attacks. SwiftNIO HTTP/2 has been affected by several of these vulnerabilities. This disclosure covers all of them.
All SwiftNIO HTTP/2 versions between 1.0.0 and 1.4.0 inclusive are affected.
Skipping call to getter when oldValue is not used in didSet
This proposal aims to make a small change to the semantics of didSet, so that the call to the property's getter is skipped if the user does not refer to the oldValue in the body of the observer.
https://forums.swift.org/t/skipping-call-to-getter-when-oldvalue-is-not-used-in-didset/27858
https://twitter.com/jckarter/status/1161298507527000064
@dgregor79 implemented a secret feature that lets you implement the wrapper as a static subscript with access to self. Use at your own risk https://github.com/apple/swift/pull/25884
Swift-package-manager on Windows? Sure Why Not!
https://forums.swift.org/t/swift-package-manager-on-windows-sure-why-not/27884
Thread Sanitizer for Swift on Linux
https://swift.org/blog/tsan-support-on-linux/
https://forums.swift.org/t/swift-org-blog-thread-sanitizer-for-swift-on-linux/27872
This maybe can be fun one https://github.com/apple/swift/pull/26650
Future directions of Property Wrappers
https://forums.swift.org/t/future-directions-of-property-wrappers/27934
[Proposal: SSWG Incubation Process Change] Discourage use of *Unsafe*
https://forums.swift.org/t/proposal-sswg-incubation-process-change-discourage-use-of-unsafe/27921
Proposal for SSWG incubation process change: add section about security requirements
LLVM is now on C++14
LLVM and clang are now compiling with C++14 as of yesterday: llvm.org/D66195 CMake projects will just inherit this build setting, but other builds will need to be updated. There's already some C++14 specific code in the LLVM codebase, so incoming merges will be broken unless all Swift builds also use C++14.
Maybe will add https://www.swiftbysundell.com/podcast/54 as it covers Swift 5.1
Maybe will add https://www.swiftbysundell.com/podcast/54 as it covers Swift 5.1
And has this funny guy right here on it as well
Building .swiftmodules for SourceKit
https://forums.swift.org/t/building-swiftmodules-for-sourcekit/28030
Default Protocol Implementation Inheritance Behaviour - The current situation and what/if anything should be done about it
To contribute to this issue, simply leave a comment here. Please also review our contributing guidelines.
The current draft for this issue in
_drafts/
. If you want to contribute directly, feel free to open a pull request.