dotnet/roslyn

IOperation: VB - Bound nodes created only during lowering phases should throw from IOperation members

Open

#8,907 opened on Feb 19, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (20,414 stars) (4,257 forks)batch import
Area-AnalyzersBugFeature - IOperationLanguage-VB_Product-level triagedhelp wanted

Description

BoundDup BoundArrayLength BoundFieldInfo BoundMethodInfo BoundReferenceAssignment BoundSequencePointExpression

Contributor guide

Tech stack
csharp
Domain
backendtooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
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.
needs investigation
Prerequisites
Roslyn compiler internalsIOperation interfaceLowering phases in C# compiler
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
The issue lists bound nodes (BoundDup, BoundArrayLength, etc.) that are created only during lowering but currently do not throw when accessed via IOperation. To resolve, examine existing IOperation implementations in the Roslyn codebase (e.g., in src/Compilers/CSharp/Portable/Lowering/) to understand the pattern. Then modify each listed node's IOperation member to throw a NotImplementedException or NotSupportedException. No linked PRs or comments exist, so the exact exception type may need clarification from maintainers.