dotnet/roslyn

Make method async : should "pull" await in the caller when possible

Open

#49,764 opened on Dec 3, 2020

View on GitHubContributor guide
 (3 comments) (1 reaction) (0 assignees)C# (4,257 forks)batch import
Area-IDEhelp wanted

Repository metrics

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

Description

Brief description:

I am not sure I am in the correct place, so feel free to redirect me.

What I'd like when I use the refactoring "make a method async", is that all callers should automatically await my method (and propagate again to their callers if it was not alredy async, recursively)

Also, I understand that is is a convention to add "Async" suffix, but it will be ideal if it can be configured somewhere (because, at the moment, I just need to rename the method after it has been made async, but with recursion it can be a lot of renames ...)

Languages applicable:

C# (I don't know if it applies to other languages)

Contributor guide

Research direction
Explore the existing 'make method async' code fix in Roslyn and design a recursive propagation of async/await through callers, considering 'Async' suffix configuration.
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.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
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#async/await concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30