dotnet/roslyn

Recommend preprocessing symbols that have already been typed out in the document

Open

#76,469 opened on Dec 17, 2024

View on GitHub
 (5 comments) (0 reactions) (0 assignees)C# (4,257 forks)batch import
Area-IDECommunityhelp wanted

Repository metrics

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

Description

Right now, typing out a preprocessing directive does not recommend any symbols aside from the standard .NET SDK ones. So if I have already typed #if SYMBOL in the document, I should be getting it recommended in expressions inside #define, #undef, #if, #elif.

The restriction for symbols within the document is only to avoid performance pitfalls, if there is no index capturing all the preprocessing symbol identifiers used in the compilation. Otherwise, it would be nice to extend this globally across the entire assembly or compilation.

Contributor guide

Research direction
Locate the completion provider for preprocessing symbols in Roslyn and modify it to include symbols defined in the current document (e.g., from #if directives) in addition to standard .NET SDK symbols.
Tech stack
csharp
Domain
developer experienceapi
Issue type
Feature
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#Roslyn
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60