dotnet/roslyn

APIs which contain oblivious nullability should indicate that in Quick Info

Open

#80875 opened on Oct 24, 2025

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

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

Tech stack
csharp
Domain
developer experiencetooling
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.
half day
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# nullabilityRoslyn IDE APIsQuick Info
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
Investigate the previous change that added the nullable oblivious warning for variable Quick Info. Identify the corresponding code for method signature Quick Info in Roslyn's IDE layer, e.g., in src/Features/LanguageServer/QuickInfo or src/EditorFeatures/Core/. Look for where signature help is generated and add similar logic to display 'oblivious' annotation for nullable parameters and return types. Review any existing tests for Quick Info to ensure the new behavior is covered.