@dotnet/jit-contrib PTAL

Related to calling methods that return values and then ignoring those return values.

@AndyAyersMS Is that situation applicable to the repro in #116180 or just the older case? I tried changing code around in the repro case to avoid this issue but haven't been able to (trying to find a workaround until this is released in servicing).

Related to calling methods that return values and then ignoring those return values.

@AndyAyersMS Is that situation applicable to the repro in #116180 or just the older case? I tried changing code around in the repro case to avoid this issue but haven't been able to (trying to find a workaround until this is released in servicing).

To the repro. I tried various source manipulations there with no luck.

It is not just that the return value is ignored; it's also that the JIT can prove that the cast to IDisposable will fail and so removes that whole bit of code, and that the return value can be trivially predicted from the argument, so when all this is inlined it creates this odd orphaned local reference that trips up forward sub.

Ah, gotcha, thanks for the explanation.

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.