You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.
Other than removing them as these things are added to Roslyn, I wonder how to handle this in the future? Does the analyser need to detect which version of the compiler it's running against and behave differently, or is there a smarter way?
The text was updated successfully, but these errors were encountered:
The "correct" way is to look at the IL, but that is expensive.
That's what I feared. BTW before I came across your analysers, I had a go at doing just this. I used Roslyn to compile the code and then Cecil to get the IL so it could be analysed.
And yes, you're right, it's expensive, even with Roslyn compiling in-memory.
edespong
added a commit
to edespong/RoslynClrHeapAllocationAnalyzer
that referenced
this issue
Dec 14, 2017
I don't know if you've seen this or not, but seems like Microsoft are getting rid of some of the scenarios that this analyser picks up.
Other than removing them as these things are added to Roslyn, I wonder how to handle this in the future? Does the analyser need to detect which version of the compiler it's running against and behave differently, or is there a smarter way?
The text was updated successfully, but these errors were encountered: