[swift-evolution] [Late Pitch] Deprecations, Moves, and Renames
me at benrimmington.com
Fri Aug 12 15:00:30 CDT 2016
> On 9 Aug 2016, at 20:09, Dave Abrahams wrote:
> Deprecate the ExpressibleByStringInterpolation protocol with a
> message indicating that its design is expected to change. We know
> this protocol to be mis-designed
> (https://bugs.swift.org/browse/SR-1260) and limited
> (https://bugs.swift.org/browse/SR-2303), but there's no time to fix it
> for Swift 3. If we knew what the new design should look like, we
> might be able to calculate that the current API is supportable in a
> forward-compatible way (as we do for Comparable). Unfortunately, we
> do not.
Can the deprecation of ExpressibleByStringInterpolation be reverted next year,
if a backwards-compatible design is proposed for Swift 4.0?
More information about the swift-evolution