microsoft / microsoft/durabletask-dotnet
Investigate state sharing between different Roslyn analyzers
Open
Nobody has claimed this yet.
Analyzer
Enhancement
P3
- Dominant language
- C#
- Stars
- 193
- Forks
- 60
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 4
Description
All analyzers currently instantiate KnownTypeSymbols. We should investigate whether there is a non-negligible performance gain when using state sharing (through TryGetValue methods) to instantiate it just once.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with src/Analyzers/KnownTypeSymbols.cs and the analyzer implementations that instantiate KnownTypeSymbols. Read Roslyn's CompilationStartAnalysisContext.TryGetValue documentation, then compare the current per-analyzer instantiation with shared state and document whether the performance gain is non-negligible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100