dotnet/roslyn

Reuse MethodDebugInfo across EvaluationContexts

Open

#1,145 opened on Mar 9, 2015

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)C# (4,257 forks)batch import
Area-InteractiveBugFeature RequestInteractive-Debugginghelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (Avg merge 6d 17h) (256 merged PRs in 30d)

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

Research direction
Investigate where EvaluationContext is created and how MethodDebugInfo is stored. Look for opportunities to cache MethodDebugInfo per method version.
Tech stack
csharp
Domain
compilers
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
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.
Mostly clear
Prerequisites
GitC#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45