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# (4,257 forks)batch import
Area-AnalyzersBugFeature - IOperationLanguage-VB_Product-level triagedhelp wanted

Repository metrics

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

Description

BoundDup BoundArrayLength BoundFieldInfo BoundMethodInfo BoundReferenceAssignment BoundSequencePointExpression

Contributor guide

Research direction
Identify where each bound node (e.g., BoundDup, BoundArrayLength) is created during lowering and ensure their IOperation implementations throw NotSupportedException or similar.
Tech stack
csharp
Domain
backend
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.
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 compiler internalsIOperation APIVisual Basic bound nodes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20