You’re “safe" here: in a library with resilience enabled, protocol extension
methods are not emitted into the client unless they’re marked @inlinable (or
however that ends up being spelled when we’re done with SE-0193).
That said, you can’t be sure someone didn’t just implement their own
‘contr
Given the tentative ideas already being worked on for ABI stability what would
be the place that code associated with a default implementation of a method on
a protocol live?
e.g.
FooKit has some code that is similar to this:
public struct SomeOptions : RawRepresentable {
public private(se
