roslyn: Strange syntax error in interpolated string when using ?:

I insist that using “?:” operator inside an interpolated string handled WRONG WAY. We waited year while you discussing proper syntax for interpolation, and now, when you introduced these clumsy {} (instead of one symbol $ ), you say “it’s not a bug”. IT IS a bug. Once you limit substitution expression with braces {}, take full responsibility to handle it properly. And nobody care on what you base your formatting - we didn’t ask you to use “string.Format” - we asked just simple substitution, like “Hello, $UserName!”.

The error will be

error CS8361: A conditional expression cannot be used directly in a string interpolation because the ':' ends the interpolation. Parenthesize the conditional expression.

@gafter: I offered same solution like Nemerle has: dollar sign + verbatim mode. Better if these strings will have different quotes. Say, backtick (like in D). Finally it will look like this:

var s = ~bacltick here~ Today is $day Temp is $temp Last line of string~bacltick here~;

It’s simple, CLEAR, obvious solution, usable for 99% cases. Where not, use old, good strings, Format(), etc. Yes, it’s not “hyper universal solution”, but I’m tired of “universal architectors”, who convert every task into idiotically complex solution (his code) and same idiotically complex usage (my code). Overengineering in other words.

Any expression, unary or sixnary, have to be completely parsed in interpolation string as a whole expression, NOT to intersecting with any “formatting” characters. It’s just stupid - introduce feature to SIMPLIFY our life and make it so abstract/clumsy that it become UNUSABLE. What organ you use to think, team?? Just keep in your student head: $“… {a ? b : c}…” MUST WORK. Period. No excuses, no annoying explanations why you didn’t make it properly.