[swift-evolution] [swift-evolution-announce] [Review] SE-0137: Avoiding Lock-In to Legacy Protocol Designs

Dave Abrahams dabrahams at apple.com
Fri Aug 12 12:50:38 CDT 2016

on Thu Aug 11 2016, Brent Royal-Gordon <swift-evolution at swift.org> wrote:

>> On Aug 10, 2016, at 2:03 PM, John McCall <rjmccall at apple.com> wrote:
>> Hello Swift community,
>> The review of "SE-0137: Avoiding Lock-In to Legacy Protocol Designs" begins now and runs through August 14. The proposal is available here:
>> 	https://github.com/apple/swift-evolution/blob/master/proposals/0137-avoiding-lock-in.md
> 	'ExpressibleByStringInterpolation' is deprecated: it will be
> replaced or redesigned in Swift 4.0.  Instead of conforming to
> 'ExpressibleByStringInterpolation', consider adding an
> 'init(_:String)'
> I'm not sure I understand this error message. What is the second
> sentence trying to imply you should do instead of conforming?

Hmm, I agree that could be clearer.  It's trying to say, “just use
string interpolations to express Strings, and give your type a
converting initializer from String.”

> Otherwise, +1 to all of this.


More information about the swift-evolution mailing list