dotnet/roslyn

Reuse MethodDebugInfo across EvaluationContexts

Open

#1,145 opened on Mar 9, 2015

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C# (20,414 stars) (4,257 forks)batch import
Area-InteractiveBugFeature RequestInteractive-Debugginghelp wanted

Description

We can only reuse the whole context if we are in the same scope, but we can reuse the MethodDebugInfo anywhere within the same version of the same method.

Contributor guide

Tech stack
csharp
Domain
performance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C# knowledgeRoslyn compiler architectureUnderstanding of debugging
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Investigate the MethodDebugInfo class and its usage in EvaluationContext. Look for opportunities to cache it per method version. Refer to similar caching patterns in the codebase. The issue is old, so check if any existing PRs or discussions have addressed this.