Notices by Ben Cohen (airspeedswift@mastodon.social), page 2

Apparently people are angry about a manifesto? Probably @dgregor79 ruling out adding higher-kinded types to swift.

Percentages add up to 100. As segfaults and exploits due to buffer overruns or use-after-frees decrease, the proportion of bugs that come down to logic errors will increase.

If the way you achieved memory safety (or performance) means your code is so ceremony-heavy that it starts to impact correctness, because you can't so easily see what it is actually trying to _do_, this is unfortunate.

Think about this now, not once we get there.

There's this increasing tendency to talk about memory safety as if, because it's the most pressing problem _right now_, solving it means you've won the battle. But that's not the end goal… it's the start. Literally the least you can do.

Whenever I read the headline “House Republicans Brace for Drawn-Out Speaker Fight” I like to imagine them having a massive argument about whether or not you can hear the difference a supertweeter makes.

Come for the safety, stay for the dry C++ humour

https://www.youtube.com/watch?v=lgivCGdmFrw

The triumphant return.

https://forums.swift.org/t/refresh-review-se-0220-count-where/66235

I am begging you to stop using forEach

I’ve wandered into an alternate universe where I'm dealing with some people who seem only capable of communicating via phone, and its murder. I email them saying we should schedule a time to talk, and they call me to try and arrange that time. I cannot answer so I email them and later that day they call me again. Send help.

Finally today you can learn about the #Swift OpenAPI Generator and how it can help wrangle HTTP APIs between apps and servers.

https://developer.apple.com/wwdc23/10171

@steve it’s the carnivorous peonies you’ve gotta watch out for

Then learn all about the new #swift macros feature from @beccadax in Expand on Swift macros

https://developer.apple.com/wwdc23/10167

And you can hear about the latest addition to Swift’s expressive generics system with Generalize APIs with parameter packs

https://developer.apple.com/wwdc23/10168

...and learn how to write your own in Write Swift macros

https://developer.apple.com/wwdc23/10166

This morning, up your #swift concurrency game with Beyond the basics of structured concurrency

https://developer.apple.com/wwdc23/10170

Today @zoecarver gets into the details of how to go between #Swift and C++ https://developer.apple.com/wwdc23/10172

And some bonus #swift content: the “Build robust and resumable file transfers” talk includes a section on building the server side of resumable uploads using SwiftNIO, complete with sample code.

https://developer.apple.com/videos/play/wwdc2023/10006/

In What's new in Swift I mention the performance improvements from the new Swift implementation of Foundation. Performance came up a lot when we first put the open source package live, but wasn't easy to talk about until the new OS betas were available.

One common trope at the time was “it isn't faster than using Objective-C, this is just to reduce Swift bridging costs” and while that's true, it's important to note Swift is _just plain faster_, as seen even when calling into it from ObjC.

Loads of great #swift content for you this week, starting with @dgregor79 and me taking you through the latest improvements in What’s new in Swift

https://developer.apple.com/wwdc23/10164

The IDE experience with swift macros is pretty great.

US default has some fun Y2K-ish consequences, since plenty of software just doesn’t account for the possibility of treasuries not just becoming inert the day after they mature.