This is only a "for your information" issue for documentation purposes.
The last update we started was dotnet/roslyn#53304. If you look at the history, it took a super-long time until it landed. That was the point in time where we decided to no longer bother to provide update PRs.
Recently, @CyrusNajmabadi started PR dotnet/roslyn#67875 (after opening issue #2965 with us), which was merged but almost immediately reverted in dotnet/roslyn#67919. I asked in comment dotnet/roslyn#67919 (comment) what/if the future process could/would be to update the decompiler, but got no answer.
So we have no insight if/when updates to our decompilation engine will land in Roslyn / VS Debugger in the future going forward (fyi @jacdavis).
This is only a "for your information" issue for documentation purposes.
The last update we started was dotnet/roslyn#53304. If you look at the history, it took a super-long time until it landed. That was the point in time where we decided to no longer bother to provide update PRs.
Recently, @CyrusNajmabadi started PR dotnet/roslyn#67875 (after opening issue #2965 with us), which was merged but almost immediately reverted in dotnet/roslyn#67919. I asked in comment dotnet/roslyn#67919 (comment) what/if the future process could/would be to update the decompiler, but got no answer.
So we have no insight if/when updates to our decompilation engine will land in Roslyn / VS Debugger in the future going forward (fyi @jacdavis).