Discussion
Loading...
Post
@konstantin Package traits (https://github.com/swiftlang/swift-evolution/blob/main/proposals/0450-swiftpm-package-traits.md) seem to be SwiftPM’s modern solution for optional package features that clients need to enable manually. I’d say a trait named “experimental” or “unstable” makes the intent pretty clear.
@ole thank you! I will check it out
@konstantin you can use compiler flags or environment variables, but IIRC they don't get passed on from Xcode app builds like they do when you build the lib from the CLI 🤔
@ctietze That's a lot of work maybe 😅. I'm asking for https://github.com/TootSDK/TootSDK/pull/392 - @dale_price had an excellent idea that we can support some "alpha" APIs from Mastodon but I want to make it clear that it's early days. One way is maybe using the underscore prefix in the name but I can't think of a solid, universally understood way of indicating experiments in Swift.
@ctietze @dale_price Oh I found this! https://varanios.com/articles/spi-or-how-to-develop-better-apis-in-swift/
A method marked with `@_spi(Experimental)` requires a `@_spi(Experimental)` to opt in. That's not bad maybe
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled