dotnet/roslyn

APIs which contain oblivious nullability should indicate that in Quick Info

Open

#80,875 opened on Oct 24, 2025

View on GitHub
 (4 comments) (1 reaction) (0 assignees)C# (4,257 forks)batch import
Area-IDEhelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (Avg merge 7d 9h) (270 merged PRs in 30d)

Description

Recently we made a change to give a heads up when interacting with nullable-oblivious variables:

It would be useful if this information were also conveyed when looking at a signature that contains oblivious nullability:

Contributor guide

Research direction
Investigate the Quick Info provider for method signatures and add indication for oblivious nullability parameters.
Tech stack
csharp
Domain
developer experience
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 SDK
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55