Hi Pieter,

Thanks for posting!

When using the ternary expression you've provided, it looks as though the compiler treats this as a single physical statement.

You'll notice this if you try to set a breakpoint on the second or third line of the statement. It'll just land at the top.

This creates a brick wall for NCrunch, as NCrunch relies on the debug data emitted by the compiler, there is no way it can differentiate between the two different values and report on them separately. As far as NCrunch is concerned, it might as well be a single method call. This means that providing what you're asking for would be impossible without making changes to the compiler itself.

I realise this is a different answer to what I've provided in the forum post you've quoted me on. When I wrote that post, I was under the assumption that placing the ternary operator across lines would allow NCrunch to break it up line-by-line. It seems this isn't the case, which means that even the moonshot solution I was contemplating back then would not be able to solve this problem.

Sorry, I realise this isn't the answer you wanted. I'm just being realistic.


Cheers,

Remco

Interesting .. I do wonder how they've done that.



Not easily. A ternary operator itself is a language-level construction that doesn't have a direct representation inside MSIL. C# basically just translates it into branches/conditions. NCrunch itself is language independent - it doesn't parse C# in any form, instead it relies on interpretation from MSIL. So it might be possible to infer the existence of a ternary operator by looking at the IL and taking a guess ... but then to show any kind of visual data about it would likely still require some form of parsing.