Re: [swift-evolution] ExpressibleByStringInterpolation

This is an excellent proposal; no suggestions for improvement at this point, as I think it has evolved excellently from its earlier forms. I hope it goes swiftly to review. On Tue, Aug 8, 2017 at 11:08 PM, Brent Royal-Gordon via swift-evolution < swift-evolution@swift.org> wrote: > I had a

Re: [swift-evolution] ExpressibleByStringInterpolation

I like the proposal so far and would be happy seeing this in 4.1, even. ;) I don’t know/remember the conditions under which the previous implementation was deemed unsuitable, but this addresses most of my personal qualms with it. My primary interests in an interpolation align with yours: in

[swift-evolution] ExpressibleByStringInterpolation

I had a proposal for replacing/reintroducing `ExpressibleByStringInterpolation` (which is currently deprecated pending a redesign), but it landed too late in the Swift 4 cycle to be considered. The PR is here: https://github.com/apple/swift-evolution/pull/659 I think it squares up relatively

Re: [swift-evolution] ExpressibleByStringInterpolation vs. String re-evaluation vs. Regex

on Mon Aug 08 2016, Jacob Bandes-Storch wrote: > Hi Dave, > I just filed https://bugs.swift.org/browse/SR-2303. > > Brainstorming: is it important that the init(stringInterpolation:) and > init(stringInterpolationSegment:) requirements are on the same type? As far as

Re: [swift-evolution] ExpressibleByStringInterpolation vs. String re-evaluation vs. Regex

Hi Dave, I just filed https://bugs.swift.org/browse/SR-2303. Brainstorming: is it important that the init(stringInterpolation:) and init(stringInterpolationSegment:) requirements are on the same type? Perhaps it would work to separate these two requirements, allowing the segments to construct

Re: [swift-evolution] ExpressibleByStringInterpolation vs. String re-evaluation vs. Regex

on Sat Jul 30 2016, Jacob Bandes-Storch wrote: > In the past, there has been some interest in refining the behavior of > ExpressibleByStringInterpolation (née StringInterpolationConvertible), for > example: > > - Ability to *restrict the types that can be used* as

Re: [swift-evolution] ExpressibleByStringInterpolation vs. String re-evaluation vs. Regex

Here's another example use case: Auto Layout visual format strings. https://gist.github.com/jtbandes/9c1c25ee4996d2554375#file-constraintcollection-swift-L85-L87 Since only views and numeric types are supported, the generic init has to be a run-time error. Ideally it could be a compile-time

Re: [swift-evolution] ExpressibleByStringInterpolation vs. String re-evaluation vs. Regex

> On Jul 30, 2016, at 10:35 PM, Jacob Bandes-Storch via swift-evolution > wrote: > > In the past, there has been some interest in refining the behavior of > ExpressibleByStringInterpolation (née StringInterpolationConvertible), for > example: > > - Ability to