Skip to content

Investigate/optimize performance of TrimAnalysisPatterns tracked by ILLink Roslyn analyzer #94312

Open
@sbomer

Description

@sbomer

The ILLink RoslynAnalyzer has various types such as TrimAnalysisMethodCallPattern and TrimAnalysisFieldAccessPattern 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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-Tools-ILLink.NET linker development as well as trimming analyzers

    Type

    No type

    Projects

    Status

    No status

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions