dotnet/roslyn

Add public compiler APIs for the /debug+ functionality

Open

#5,410 opened on Sep 23, 2015

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (20,414 stars) (4,257 forks)batch import
Area-CompilersBugConcept-APIhelp wanted

Description

This is related to https://github.com/dotnet/roslyn/issues/4103

Generally if something can be done via command line switches, there is also a way to do that via compiler APIs.

Contributor guide

Tech stack
csharp
Domain
apitooling
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.
over 1 week
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.
unclear
Prerequisites
C# language proficiencyRoslyn compiler internalsUnderstanding of /debug+ flag
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Begin by reading the linked issue #4103 to understand the motivation. Explore the Roslyn compiler codebase, particularly the CommandLineParser and related API classes. Look for existing patterns of exposing command line options as public APIs. Then draft a proposal for the new APIs, considering how they integrate with the existing Compilation and CSharpCompilation classes. Note that no comments or PRs exist on this issue, so you'll need to gather context from the referenced issue and the code.
Add public compiler APIs for the /debug+ functionality · dotnet/roslyn#5410 | Good First Issue