Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mamot.fr is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mamot.fr est un serveur Mastodon francophone, géré par La Quadrature du Net.

Administered by:

Server stats:

3.1K
active users

mamot.fr: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

#swiftlang

27 posts12 participants1 post today
Public
Becca Royal-Gordon

Ever wanted to form a key path to a method or initializer? The authors of SE-0479 did too! Their proposal is in review: forums.swift.org/t/se-0479-met #SwiftLang

Swift Forums · SE-0479: Method and Initializer Key PathsHello Swift community, The review of "Method and Initializer Key Paths" begins now and runs through May 5, 2025. The proposal is available here: swift-evolution/proposals/0479-method-and-initializer-keypaths.md at main · swiftlang/swift-evolution · GitHub Reviews are an important part of the Swift evolution process. All review feedback should be either on this forum thread or, if you would like to keep your feedback private, directly to the review manager by email or Swift Forums DM. When c...
Public
Ole Begemann

Reminder that SwiftPM package manifests are Swift code, so you can write loops etc. in them. I use this in some of my packages to enable the same upcoming language features for all targets. Example: gist.github.com/ole/c0f4de915a

This isn’t particularly useful for complex projects where you might want to migrate to Swift 6 mode module-by-module, but for small and simple packages it’s usually easy to stay on the cutting edge of Swift. #SwiftLang

Swift code: let upcomingFeaturesPostSwift6: [SwiftSetting] = [ .enableUpcomingFeature("ExistentialAny"), .enableUpcomingFeature("InternalImportsByDefault"), .enableUpcomingFeature("MemberImportVisibility"), ] for target in package.targets { guard target.type != .binary else { continue } var swiftSettings = target.swiftSettings ?? [] swiftSettings.append(contentsOf: upcomingFeaturesPostSwift6) target.swiftSettings = swiftSettings }
Public
Cihat Gündüz

Introducing a new open-source #Swift package that I've been working on for 8 months! Say hello 👋 to #ErrorKit – a set of APIs that simplify #ErrorHandling in Swift 6. Built to be actually helpful, not only for large teams but also for #IndieDev's like myself. And boy have I documented it! 💯

Please check it out & give it a ⭐️ on GitHub: #iOSDev #SwiftLang
github.com/FlineDev/ErrorKit

Simplified error handling with built-in user-friendly messages for common errors. Fully localized. Community-driven. - FlineDev/ErrorKit
GitHubGitHub - FlineDev/ErrorKit: Simplified error handling with built-in user-friendly messages for common errors. Fully localized. Community-driven.Simplified error handling with built-in user-friendly messages for common errors. Fully localized. Community-driven. - FlineDev/ErrorKit
Public
David Smith

Periodic reminder that `Task.detached` is semantically equivalent to `DISPATCH_BLOCK_DETACHED`. e.g. it opts out of automatic priority propagation, task locals, cancellation, etc…

So far 100% of the time I've mentioned this the response has been "what's DISPATCH_BLOCK_DETACHED?", which should give you an idea of how rare uses of `Task.detached` should be.

As the docs say: "Don’t use a detached task if it’s possible to model the operation using structured concurrency features"

#swiftlang
Public *
Puppethead

For macOS logging I'm trying to use the recommended bundle ID as the OSLog subsystem, so I use the following code snippet. But it seems like I might as well hardcode the subsystem since bundleIdentifier might be nil. Is there a better way to get the bundle ID (or PRODUCT_NAME) in code?

extension Logger {
static let subsystem = Bundle.main.bundleIdentifier ?? "org.foo.MyApp"
}

#SwiftLang#macOSDev
Public
Becca Royal-Gordon

Forgot to mention this the other day, but the @abi proposal is in review! I think the approximately ten people who will use this feature will be very happy with it. #SwiftLang forums.swift.org/t/se-0476-con

Swift Forums · SE-0476: Controlling the ABI of a function, initializer, property, or subscriptHello, Swift community! The review of SE-0476: Controlling the ABI of a function, initializer, property, or subscript begins now and runs through April 25th, 2025. Reviews are an important part of the Swift evolution process. All review feedback should be either on this forum thread or, if you would like to keep your feedback private, directly to me as the review manager by email or DM. When contacting the review manager directly, please put "SE-0476" in the subject line. Trying it out If you...
ExploreLive feeds
About