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