String interpolation works fine in this case:
val name = "Bill"
val result = s"My Name is ${name}"
When I introduce it to the variable it didn't get interpolated value:
val name = "Bill"
val greeting = "My Name is ${name}"
val result = s"${greeting}"
Direct wrapping of greeting is not appropriate solution, I must handle greeting like a plain String.
String interpolation in Scala does not compose in the way you expect.
The issue for this has been debated. Folks want it, but folks don't always get what they want.
You could imagine writing some macros that work in concert. One defines a function taking a string, the other knows how to interpolate it by invoking it with the correctly named value in scope.
Also worth adding that interpolation is not a generic runtime templating mechanism. For example, you can't read strings from a file of the form "$greeting" and run interpolation substitutions on it.
name with value "Bill"String variable greeting which contains characters ['M','y',' ','n','a','m','e',' ','i','s',' ','$','{','n','a','m','e','}'] (completely unrelated to the variable name, the four characters 'n', 'a', 'm', 'e' have no possibility of getting anywhere near compiler's symbol table, which is good).There is a variable result, whose value is computed by string interpolation from greeting. Since
val y = "whatever"
val x = s"${y}"
must always result in variable x having the same content as variable y, the variable result ends up having the same value as greeting, namely "My Name is ${name}".
If the compiler tried to execute every substring that looks somewhat like Scala code, this would result in total chaos, because every time something can leak from the realm of String-data into the realm of executable code, it makes the code vulnerable for all kind of injection exploits.
greetingmakes no sense, as it's already a string(name: String) => s"My Name is ${name}"? Or do you wantnameto be bound dynamically to whichever variable called name is in scope at the time you calls"${greeting}"? Hint: go with the function either way. It's far less confusing.resultis expected, and it's OK not to care what the type ofgreetingis, just as users don't care what the expressions"$greeting"actually does.