Simplified syntax for null-coalescing operator

[luis-j-soares]

I was showcasing ternary and null-coalescing operators in a workshop today, and this question came up: "why is ternary turning simple expressions into if/else statements, but null-coalescing doesn't?"

So we could take #1341 and extend it to null-coalescing expressions.

chosenUser = user ?? {}

' transpiles to...

chosenUser = bslib_coalesce(user, {})

' but it could transpile to...

chosenUser = user
if chosenUser = invalid
    chosenUser = {}
end if

[TwitchBronBron]

Definitely! I was just trying to keep the scope focused when landing that. The exact same logic should be applicable for this.

Would you have any bandwidth to try and port that logic over for this feature?

[luis-j-soares]

I can give it a go, for sure!

[TwitchBronBron]

Summary of what needs to be done:

• port the if/else transpile logic used in ternary over to the null coalescing operator (implemented in Optimize ternary transpilation for assignments #1341)
• add the same volume of unit tests for this new feature