Investigate/optimize performance of TrimAnalysisPatterns tracked by ILLink Roslyn analyzer #94312
Labels
area-Tools-ILLink
.NET linker development as well as trimming analyzers
Milestone
The ILLink RoslynAnalyzer has various types such as
TrimAnalysisMethodCallPattern
andTrimAnalysisFieldAccessPattern
used to track relevant "patterns" that may produce dataflow warnings. Tracking such values is potentially expensive, especially now that we do it even for values which may not be relevant for dataflow, just to track their types, after #93732.On top of that, #94123 is introducing additional context to the tracked patterns to track the "feature context" of the invocation/field access/etc.
We should investigate the performance of this approach and consider ways to optimize it.
Context: #94123 (comment)
The text was updated successfully, but these errors were encountered: