Skip to content

Do not recommend async if such modifier is already present#60412

Merged
CyrusNajmabadi merged 1 commit intodotnet:mainfrom
DoctorKrolic:not-recommend-async-if-already-present
Mar 28, 2022
Merged

Do not recommend async if such modifier is already present#60412
CyrusNajmabadi merged 1 commit intodotnet:mainfrom
DoctorKrolic:not-recommend-async-if-already-present

Conversation

@DoctorKrolic
Copy link
Copy Markdown
Contributor

Fixes: #60340

Note: while async async can be valid in some cases, the second async is never a keyword, so AsyncKeywordRecommender should exclude it in such cases anyway

@DoctorKrolic DoctorKrolic requested a review from a team as a code owner March 27, 2022 17:14
@ghost ghost added Community The pull request was submitted by a contributor who is not a Microsoft employee. Area-IDE labels Mar 27, 2022
Copy link
Copy Markdown
Contributor

@CyrusNajmabadi CyrusNajmabadi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@CyrusNajmabadi CyrusNajmabadi merged commit e721c94 into dotnet:main Mar 28, 2022
@ghost ghost added this to the Next milestone Mar 28, 2022
@DoctorKrolic DoctorKrolic deleted the not-recommend-async-if-already-present branch March 28, 2022 04:37
@allisonchou allisonchou modified the milestones: Next, 17.2.P3 Mar 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-IDE Community The pull request was submitted by a contributor who is not a Microsoft employee.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Odd behaviour with async method declaration: bad keyword suggestion

4 participants