Márton Balassa

Maybe I'm missing some parsing aspect, but what's wrong with simply writing this: ```cs if (x in (1, 2, 3)) {} ``` which would be lowered to ```cs if (x...

#4108 would cover ranges perfectly: ```cs if (1 < x

@jeskew I could live with variable typing being only a compile-time check.

> As a workaround, have you considered using splatting syntax That was just an example minimal repro case. In reality I'm calling Azure PowerShell functions having all sorts of parameters.

The weirdest thing is that the link works when the exception is at the top of the stack (eg. an assertion failed).

@rprouse I've repeated the steps with Xunit and the stack trace links are working. I believe it is a NUnit-related issue.

I don't know if I should open a new issue for this, but I see a different anomaly with test durations. Test duration seems to be random (or nothing, 1ms...