How can it be breaking changes?

In the current code, ternary operator only work onbool expression and error when it used on expression that result onbool?, so there should be nowhere using it on any expression that not return exact true or false

If this suddenly work it should affect no existing code that can compiled properly, instead it will only affect new code

usingSystem;publicclassC{publicvoidM(){int?maybeCondition=null;varv=maybeCondition>0?1:2;}}

This is already legal code. 'v' is an int. It cannot become anint? (or null) just becausemaybeCondition is null.

@CyrusNajmabadi Oh right, sorry, I forgot((int?)null) > 0 is not result in nullable, it just normal bool and false, and I don't intend to change that, it was actually sample code unrelated to my proposal

Let me change the example code a bit

Yes, I have already write this way at first. And I felttruefalsenull and=> is unnecessary annoying and distracted when it always have just these 3 states