dotnet/roslyn

VS Immediate Window (expression compiler) ignores stamenents after semicolon

Open

#56,976 opened on Oct 6, 2021

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)C# (4,257 forks)batch import
Area-InteractiveBughelp wanted

Repository metrics

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

Description

Version Used: Visual Studio 2019 v16.11.4.

Steps to Reproduce:

  1. Start debugging of any project.
  2. Enter any multi-statement line into the Immediate Window. For example, int i = 3; i = 1337;
  3. Press Enter.
  4. Enter the expression i and press Enter again, to examine the current value of the variable.

Expected Behavior: Immediate Window should execute every statement and tell me that i = 1337.

Actual Behavior:

int i = 3; i = 1337;
Expression has been evaluated and has no value
i
3

image

Notably, if I enter a slightly different statements:

i = 3; i = 1337;

then the expression compiler generates an error message:

error CS1073: Unexpected token ';'

Contributor guide

Research direction
Examine the expression compiler's handling of semicolons in the Immediate Window.
Tech stack
csharp
Domain
developer experience
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-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#Visual Studio
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40