New SIP-24, backticks in string interpolation

[Kevin Wright]

Pull request here:

https://github.com/scala/scala.github.com/pull/297

Looking at the queue though, it seems as though pull requests aren't getting much love.

Would someone suitably acquainted with the current setup be able to glance over the current docs for SIP submission and make sure that they aren't missing any other steps I needed?

[Denys Shabalin]

Enhanced variant of the proposal isn't very compatible with quasi-quotes unfortunately.

--
You received this message because you are subscribed to the Google Groups "scala-internals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-interna...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Kevin Wright]

Forgot to add.  The formatted document can be read directly on Github here:

https://github.com/kevinwright/scala.github.com/blob/master/sips/pending/_posts/2014-02-08-backticks-in-string-interpolation.md

[Jason Zaugg]

On Sat, Feb 8, 2014 at 11:35 PM, Kevin Wright <kev.lee...@gmail.com> wrote:

I don't see a problem with s"$`a b c`". I'm against the extended proposal, though.

There is another proposal floating around to fill a hole in interpolation: to add a new escape: $"

https://issues.scala-lang.org/browse/SI-6476

https://groups.google.com/forum/#!msg/scala-internals/_DnZGO-4NXc/xNoiOUoCf58J

Kevin, would you like to incorporate that into the SIP so both could be discussed together?

-jason

[Kevin Wright]

Sure, I can add that :)

I also have another enhanced variant that I've been mulling over,to use guillemets (french/angle quotes) for interpolation.  Some of the examples previously seen would then become:

s"implicit def hlistTupler«arity»[«A..N»] : Aux[«A::N», «(A..N)»] = ..."
s"I am «qual»body"

val `"` = '"'
s"a=«"»$a«"»"

In this form, I'd only allow string-literal identifiers and not full expressions - so as to avoid ambiguity in parsing.

The precedent has already been set for using unicode characters with arrows for lambdas and in comprehensions, so this doesn't seem *too* shocking to me.  There would still, potentially, be a some already featuring angle-quotes in interpolated strings. So even this proposal isn't entirely risk-free.

--
You received this message because you are subscribed to the Google Groups "scala-internals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-interna...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
Kevin Wright
mail: kevin....@scalatechnology.com
gtalk / msn : kev.lee...@gmail.com

quora: http://www.quora.com/Kevin-Wright

google+: http://gplus.to/thecoda

twitter: @thecoda

vibe / skype: kev.lee.wright

steam: kev_lee_wright

"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra

[Jason Zaugg]

On Mon, Feb 17, 2014 at 3:03 PM, Kevin Wright <kev.lee...@gmail.com> wrote:

Sure, I can add that :)

I also have another enhanced variant that I've been mulling over,to use guillemets (french/angle quotes) for interpolation.  Some of the examples previously seen would then become:

s"implicit def hlistTupler«arity»[«A..N»] : Aux[«A::N», «(A..N)»] = ..."
s"I am «qual»body"

val `"` = '"'
s"a=«"»$a«"»"

In this form, I'd only allow string-literal identifiers and not full expressions - so as to avoid ambiguity in parsing.

The precedent has already been set for using unicode characters with arrows for lambdas and in comprehensions, so this doesn't seem *too* shocking to me.  There would still, potentially, be a some already featuring angle-quotes in interpolated strings. So even this proposal isn't entirely risk-free.

In my opinion, having a $ before every interpolation is something we should keep. Its consistent with string interpolation from other languages, as is use of ${} when whitespace isn't enough to demarcate the end of the identifier.

-jason

[virtualeyes]

Interesting, I don't have a burning need for backticks, but I'll agree that they are slightly more readable.

However, s"$foo" and s"${foo}" won't surprise new comers (of course s"$foo.bar" will ;-))