-
Notifications
You must be signed in to change notification settings - Fork 49
[146] Issue #146 - October 24, 2019 #480
Comments
|
New project announcement: Swift compiler driver reimplementation in Swift
|
Un-gitignore CMakeCache.txt
https://forums.swift.org/t/un-gitignore-cmakecache-txt/29712 |
Improving the representation of polymorphic interfaces in SIL with "substituted function types"
|
Swift 5.1.1 is now available for download. It is a bug-fix release that addresses a security issue on Ubuntu platforms. https://forums.swift.org/t/swift-5-1-1-released-linux-only/29732 |
@fassko I already included that one (last-minute!) in the previous issue 😄 |
Heads up about potential update-checkout failures for fetches from the clang, llvm, compiler-rt, libcxx, clang-tools-extra, lldb repos
|
Discussion about Source compatibility |
[Accepted] SE-0266: Synthesized Comparable conformance for enum types
https://forums.swift.org/t/accepted-se-0266-synthesized-comparable-conformance-for-enum-types/29854 |
https://forums.swift.org/t/returned-for-revision-se-0264-standard-library-preview-package/29865 |
Starter task SR-11619 [Compiler] Spurious error "anonymous closure argument not contained in a closure" in |
Backwards-deployable Conformances
https://forums.swift.org/t/backwards-deployable-conformances/29876 |
https://twitter.com/jckarter/status/1184904575435755520
|
The GitHub swift-specific split llvm-project repositories are now read-only
|
Swift on the Server Work Group October 8th, 2019 meeting notes |
Pitch: Add RangeSet and Related Collection Operations Here's a pitch to fill a missing chunk of functionality in the standard library around noncontiguous ranges of elements. Please take a look at the draft proposal below, and/or try out this new functionality by using the SwiftPM package here: https://github.com/natecook1000/swift-evolution/tree/rangeset_and_friends https://forums.swift.org/t/pitch-add-rangeset-and-related-collection-operations/29961 |
Starter task TF-935 [Autodiff] [AD] Add |
Trajectory for evaluating adding Automatic Differentiation to Swift
https://forums.swift.org/t/trajectory-for-evaluating-adding-automatic-differentiation-to-swift/30048 |
SE-0267 —
https://forums.swift.org/t/se-0267-where-clauses-on-contextually-generic-declarations/30051 |
SE-0268: Refine didSet Semantics
https://forums.swift.org/t/se-0268-refine-didset-semantics/30049 |
[Accepted] SE-0263 ‘Add a String Initializer with Access to Uninitialized Storage’ The proposal SE-0263 has been accepted. |
Apple’s engineering director, Josh Shaffer, gives deep dive on SwiftUI in new podcast |
Instance-level polymorphism I've seen some similar ideas discussed on the forums (notably Polymorphic methods in enums) which are focused around the idea of improving the experience of attaching case-specific behavior to enums without having a totally fragmented implementation. I encountered this issue yet again yesterday and wanted to solicit feedback on some thoughts I had about potential solutions. https://forums.swift.org/t/instance-level-polymorphism/30087 |
Autolinking enabled on GitHub for bugs.swift.org issues! https://forums.swift.org/t/autolinking-enabled-on-github-for-bugs-swift-org-issues/30091 |
SwiftUI Layout System: An In-Depth Look Sent with GitHawk |
https://twitter.com/johannesweiss/status/1187045920409444353
|
https://twitter.com/johannesweiss/status/1187072832552890368
|
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.The text was updated successfully, but these errors were encountered: