Skip to content

Issues: dotnet/roslyn

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
20 Open 1,133 Closed
20 Open 1,133 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Slice using range directly after stackalloc triggers CS1575 Area-Compilers Resolution-By Design The behavior reported in the issue matches the current design
#74960 opened Aug 30, 2024 by JakeYallop
5
CS1591 Thinks "protected" is public Area-Compilers Concept-Diagnostic Clarity The issues deals with the ease of understanding of errors and warnings. Question Resolution-By Design The behavior reported in the issue matches the current design
#68863 opened Jul 3, 2023 by RadicalErin Backlog
2
Use of possibly unassigned field '_dummyPrimitive' (with sharplab) Area-Compilers Concept-Diagnostic Clarity The issues deals with the ease of understanding of errors and warnings. help wanted The issue is "up for grabs" - add a comment if you are interested in working on it Resolution-By Design The behavior reported in the issue matches the current design
#67212 opened Mar 7, 2023 by AnorZaken Backlog
7
Incorrect NRT tooltip when doing null check Area-IDE Feature - Nullable Semantic Model Nullable Semantic Model Issues Resolution-By Design The behavior reported in the issue matches the current design
#66854 opened Feb 13, 2023 by vsfeedback Backlog
@jasonmalinowski
10
XML Documents for Positional Records don't show example property Area-Compilers Feature Request Resolution-By Design The behavior reported in the issue matches the current design
#62611 opened Jul 13, 2022 by Markemp Backlog
10
<exception> tag does not limit available cref symbols to exceptions Area-Compilers Language-C# Resolution-By Design The behavior reported in the issue matches the current design
#59257 opened Feb 3, 2022 by Rekkonnect Backlog
3
Positional patterns on tuple inputs leads to confusion Area-Compilers Area-Language Design Resolution-By Design The behavior reported in the issue matches the current design
#58650 opened Jan 5, 2022 by jcouv Backlog
@jcouv
1
Duplicated project when reading sln when multiple TargetPlatforms are specified Area-IDE IDE-MSBuildWorkspace MSBuildWorkspace Question Resolution-By Design The behavior reported in the issue matches the current design
#56806 opened Sep 28, 2021 by iamKunal Backlog
3
No way to suppress CS8655 (switch is not exhaustive on null) Area-Compilers Feature - Nullable Reference Types Nullable Reference Types Resolution-By Design The behavior reported in the issue matches the current design
#56699 opened Sep 24, 2021 by TessenR Backlog
10
MemberNotNullWhenAttribute doesn't work on properties from base class? Area-Compilers Concept-Diagnostic Clarity The issues deals with the ease of understanding of errors and warnings. Resolution-By Design The behavior reported in the issue matches the current design
#56531 opened Sep 19, 2021 by SoftCircuits
@jcouv
5
Analyzers - Nullable incorrectly flags null even if checked for non-null Area-Compilers Feature - Nullable Reference Types Nullable Reference Types Resolution-By Design The behavior reported in the issue matches the current design
#56064 opened Aug 31, 2021 by apsthisdev
5
Using property marked with MemberNotNullWhen to a NotNull value doesn't get rid of the warning Area-Compilers Feature - Nullable Reference Types Nullable Reference Types Resolution-By Design The behavior reported in the issue matches the current design
#55664 opened Aug 17, 2021 by krwq Backlog
1
@jcouv
1
Integration tests take a long time to fail Area-Infrastructure Resolution-By Design The behavior reported in the issue matches the current design
#53257 opened May 7, 2021 by RikkiGibson Backlog
@RikkiGibson
5
CS0023 on Null-coalescing operator for generic type. Area-Compilers Concept-Diagnostic Clarity The issues deals with the ease of understanding of errors and warnings. Resolution-By Design The behavior reported in the issue matches the current design
#49652 opened Nov 29, 2020 by jeremyVignelles Backlog
1
Roslyn's nullable analysis should skip conditional invocations that won't be emitted Area-Compilers Feature - Nullable Reference Types Nullable Reference Types Resolution-By Design The behavior reported in the issue matches the current design
#43681 opened Apr 25, 2020 by TessenR
1
CS8602 false positive due to inferred generic type argument being nullable Area-Compilers Area-Language Design Feature - Nullable Reference Types Nullable Reference Types Resolution-By Design The behavior reported in the issue matches the current design
#41705 opened Feb 14, 2020 by AArnott
@jcouv
8
Roslyn should always warn about passing nullable reference to a non-nullable reference Area-Compilers Feature - Nullable Reference Types Nullable Reference Types Resolution-By Design The behavior reported in the issue matches the current design
#36769 opened Jun 26, 2019 by TessenR Backlog
3
Roslyn should verify state of byref arguments at the moment of an invocation instead of evaulation the argument itself Area-Compilers Feature - Nullable Reference Types Nullable Reference Types Resolution-By Design The behavior reported in the issue matches the current design
#36768 opened Jun 26, 2019 by TessenR Backlog
1
Missing warning with default expression converted to tuple Area-Compilers Bug Feature - Nullable Reference Types Nullable Reference Types Resolution-By Design The behavior reported in the issue matches the current design
#35815 opened May 20, 2019 by gafter Backlog
5
Missing an option between "Prefer var for built-in types" and "when variable type is apparent" Area-IDE Feature Request Resolution-By Design The behavior reported in the issue matches the current design
#23714 opened Dec 11, 2017 by davkean Backlog
8
ProTip! Type g i on any issue or pull request to go back to the issue listing page.