A bit late to the party, but yes. Although, in true Java form the designers sacrificed readability to satisfy lesser use-cases.
STR.”Total: \{count}”
Could not get uglier.
STR.”Total: \{count}”
Could not get uglier.
C# $"{x} plus {y} equals {x + y}"
Visual Basic $"{x} plus {y} equals {x + y}"
Python f"{x} plus {y} equals {x + y}"
Scala s"$x plus $y equals ${x + y}"
Groovy "$x plus $y equals ${x + y}"
Kotlin "$x plus $y equals ${x + y}"
JavaScript `${x} plus ${y} equals ${x + y}`
Ruby "#{x} plus #{y} equals #{x + y}"
Swift "\(x) plus \(y) equals \(x + y)"
And finally:
Java STR."\{x} plus \{y} equals \{x + y}"
> trading off a small amount of convenience to gain a large amount of safety
*small
FormattableString foo = $"select * from {table} where {column} = 42";
Bad example. JavaScript literally has that (ever since ES6). [1]
function sql(strings, ...args) {
// ...
}
sql`SELECT * FROM user WHERE email = $1`
It remember me the first proposed syntax for lambdas. Let's hope the next preview will fix that.
1. https://github.com/manifold-systems/manifold/tree/master/man...
sigh
Java is my most ambivalent language. There's things I love, and things I hate, and when it's good it's really good, when it's bad ... Yuck.
That said, I do think Python went worse with f-strings. Would have loved to see Java look to Groovy for inspiration.