dotnet/roslyn

VB await in a non-async method causes string interpolation to fail to parse

Open

#3,547 opened on Jun 16, 2015

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C# (20,414 stars) (4,257 forks)batch import
Area-CompilersBughelp wanted

Description

Watch this: awaitinterpolation

When you have await in a non-async method, then string interpolations on the same line don't parse correctly!

Contributor guide

Tech stack
None
Domain
tooling
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.
over 1 week
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.
clear
Prerequisites
Familiarity with Visual Basic syntax
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Focus on the Visual Basic parser in Roslyn, specifically how string interpolation is parsed in non async methods containing 'Await' expressions. Examine the SyntaxParser or related files for VB. Check existing comments on this issue for any prior investigation or leads.