Some really impressive work from my teammate Kevin here: https://forums.swift.org/t/the-future-of-serialization-deserialization-apis/78585
If you care about Codable and/or serialization in Swift in general, definitely check it out
#SwiftEvolution
(That is, inside the struct, I just didn't have enough letters to duplicate the rest of the struct) #swiftlang #swiftEvolution
Any of you interested in adding “case” for RawRepresentable structs to Swift?
I.e. if you're simulating an enum-like open struct using
struct Foo: RawRepresentable {
var rawValue: Int
static var bar = Foo(rawValue: 0)
static var baz = Foo(rawValue: 1)
static var boff = Foo(rawValue: 999)
}
you can instead do ‘em as
case bar
case baz
case boff = 999
Like for an enum. Bonus points if you make associated values work, I'm not sure I'd know how.
My first swift evolution pitch in a while, and my first Linux pitch ever :D
https://forums.swift.org/t/pitch-io-uring-support-in-swift-system-on-linux/78340
Very exciting proposal from @glessard that I've been helping do infrastructure work in support of: https://forums.swift.org/t/se-0456-add-span-providing-properties-to-standard-library-types/77233
TLDR: safer alternative to withContiguousStorage/withBytes style methods that also eliminates the annoying pyramid of closures!
My favorite Thanksgiving tradition is a good language design debate ahead of the holiday. This time on improving the approachability of data-race safety: https://forums.swift.org/t/prospective-vision-improving-the-approachability-of-data-race-safety/76183
I care deeply about this problem, and I appreciate any thoughts, questions, and other constructive feedback you have to share!
If you’re into #SwiftLang or curious about where #SwiftEvolution is heading, don’t miss my summary of the past six months! 🚀
Concise proposals, must-see pitches, and more—check it out: 👇👇 #Swift #SwiftLanguage #iOSDev
🎉 New issue is out now! Covering all #SwiftEvolution highlights from May to November 2024:
– 6 summarized #SwiftLang proposals
– 10 noteworthy pitch links you shouldn’t miss
– A new way to follow the language’s changes
…and more!
Dive in now: 👇
https://www.fline.dev/swift-evolution-monthly-may-november-2024/
Every year, after #WWDC, I see myself considering to get on EVO App development, but life happens and always take my focus out of it. Does is it a still valid project?
The next issue is out now! Covers the best of #SwiftEvolution from January to April 2024: 📰
– Swift 6 announcement & new steering group
– Summarizes 4 accepted proposals & links to 6
– Links to 10 proposals in progress & 10 active pitches
Read now: 👇
https://www.fline.dev/swift-evolution-monthly-february-april-2024/?ref=iosdev.space
The January issue is out now! 📰
Accepted proposal summaries:
– Low-Level Atomics
– Various Concurrency Improvements
Plus: 8 more proposals & 11 exciting discussions linked.
Don’t miss out on the latest #Swift advancements!
https://fline.dev/swift-evolution-monthly-january-24/?ref=iosdev.space
I appreciate the problem that SE-0420 is trying to solve (e.g., addressing the overcorrection of SE-0338), but I find the proposed implementation disquieting. As I read it, they’re proposing that you include a parameter (that is never explicitly used) and that will change the asynchronous context under which the function runs. This would be better as a qualifier on the function itself, not just having a random parameter affect the broader execution context. #SwiftEvolution
🚀 The latest issue is out!
Accepted proposal summaries:
– Typed Throws
– Nested Protocols
– Import access modifiers
Plus: 14 additional proposals & 5 discussions linked. 🔗
Don’t miss out on the latest #Swift advancements! 📚
https://www.fline.dev/swift-evolution-monthly-december-23/?ref=iosdev.space
📧 June issue of @SwiftEvolutionM is out!
– WWDC Aftermath
– 2 new Proposals & 10 Pitches linked
– Networking Library replacement by Apple
More:👇👇👇
https://www.fline.dev/swift-evolution-monthly-june-23/?ref=iosdev.space
Huh, I haven't been following new #SwiftEvolution proposals lately… The "noncopyable" section is some crazy stuff 😲 https://www.hackingwithswift.com/articles/258/whats-new-in-swift-5-9 #Swift
Over the course of last year, I've summarized a whopping 50 #SwiftEvolution proposals as part of @SwiftEvolutionM! 🤯
You can now find all my summaries here on GitHub:
https://github.com/FlineDev/swift-evolution
Or simply replace "apple" in the URL with "FlineDev" when you have a proposal open.
Learn more here:
https://www.fline.dev/swift-evolution-monthly-mar-apr-23/?ref=iosdev.space
Parameter packs are under review now in #SwiftEvolution
Parameter packs are a new kind of type-level and value-level entity that enable arity abstraction in generic code. The first step toward variadic generics in #SwiftLang!
https://forums.swift.org/t/se-0393-value-and-type-parameter-packs/63859
More than 50 comments in 4h of a #SwiftEvolution pitch! Is the community growing or things are just controversial? #SwiftLang 😆
@pointfreeco Also it’s really smart that the @pointfreeco guys are pointing out the lacking parts in #Swift which could make #TCA even more concise. Because it both reminds contributors to #SwiftEvolution to consider the changes, ans viewers are made aware of potential future simplifications.
There is a #SwiftEvolution proposal for a `package` access level modifier, for things accessible inside an SPM package (wider than `internal`, but not public). Although, strangely, subclassing would still only work within the module (which I'm not a big fan of). Review technically until Feb 8, but discussion is still going on: https://forums.swift.org/t/se-0386-package-access-modifier/62808 #SwiftLang
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst