Search results

Preprocessors are not put on their own line during code formatting

Area-IDE

Question

Resolution-AnsweredThe question has been answeredThe question has been answered

Resolution-By DesignThe behavior reported in the issue matches the current designThe behavior reported in the issue matches the current design

Status: Not planned (skipped).

#76566 In dotnet/roslyn;

· by SteveDunn was closed on Dec 26, 2024

"Requires unsafe context" error in an unsafe iterator

Area-Compilers

Feature - Ref/Unsafe in Iterators/Async

Resolution-By DesignThe behavior reported in the issue matches the current designThe behavior reported in the issue matches the current design

Status: Closed (completed).

#76514 In dotnet/roslyn;

· by xparadoxical was closed on Dec 28, 2024

IDE0058 triggers on expressions with 'out' params

Area-IDE

Feature - IDE0058

Question

Resolution-AnsweredThe question has been answeredThe question has been answered

Resolution-By DesignThe behavior reported in the issue matches the current designThe behavior reported in the issue matches the current design

Status: Closed (completed).

#76477 In dotnet/roslyn;

· by AbakumovAlexandr was closed on Dec 18, 2024

The warning about yield return in lock statements (CS9237) is documented in reference but not implemented.

Area-Compilers

Resolution-By DesignThe behavior reported in the issue matches the current designThe behavior reported in the issue matches the current design

Status: Not planned (skipped).

#76442 In dotnet/roslyn;

· by Akeit0 was closed on Dec 17, 2024

Unexpected error "feature 'ref struct interfaces' is not available"

Area-Compilers

Concept-Diagnostic ClarityThe issues deals with the ease of understanding of errors and warnings.The issues deals with the ease of understanding of errors and warnings.

Feature - RefStructInterfaces

Resolution-By DesignThe behavior reported in the issue matches the current designThe behavior reported in the issue matches the current design

Status: Closed (completed).

Bug

#76401 In dotnet/roslyn;

· by jjonescz was closed on Jan 3, 2025

 ·  

17.14

Compilation error involving dynamic parameter not being detected

Area-Compilers

Resolution-By DesignThe behavior reported in the issue matches the current designThe behavior reported in the issue matches the current design

Status: Not planned (skipped).

#76322 In dotnet/roslyn;

· by mus65 was closed on Dec 10, 2024

Potential missed case with CS1918

Area-Compilers

Resolution-By DesignThe behavior reported in the issue matches the current designThe behavior reported in the issue matches the current design

Status: Not planned (skipped).

#76278 In dotnet/roslyn;

· by hamarb123 was closed on Dec 10, 2024

Tuple item "field" is not properly named in property accessor

Area-Compilers

Feature - Field Keyword

Resolution-By DesignThe behavior reported in the issue matches the current designThe behavior reported in the issue matches the current design

Status: Not planned (skipped).

#76210 In dotnet/roslyn;

· by jhinder was closed on Dec 2, 2024

Infallible var pattern causes "not all code paths return a value"

Area-Compilers

Resolution-By DesignThe behavior reported in the issue matches the current designThe behavior reported in the issue matches the current design

Status: Not planned (skipped).

#76059 In dotnet/roslyn;

· by NinoFloris was closed on Nov 27, 2024

CS8604 FP with static partial class

Area-Compilers

Resolution-By DesignThe behavior reported in the issue matches the current designThe behavior reported in the issue matches the current design

Status: Closed (completed).

#75954 In dotnet/roslyn;

· by shuebner was closed on Nov 19, 2024

Formatting within #if #else #endif Statements

Area-IDE

IDE-FormatterCode formatter and/or smart indentCode formatter and/or smart indent

Resolution-By DesignThe behavior reported in the issue matches the current designThe behavior reported in the issue matches the current design

untriagedIssues and PRs which have not yet been triaged by a leadIssues and PRs which have not yet been triaged by a lead

Status: Not planned (skipped).

#75054 In dotnet/roslyn;

· by vsfeedback was closed on Sep 11, 2024

Incorrect nullability analysis

Area-Compilers

Feature - Nullable Reference TypesNullable Reference TypesNullable Reference Types

Resolution-By DesignThe behavior reported in the issue matches the current designThe behavior reported in the issue matches the current design

untriagedIssues and PRs which have not yet been triaged by a leadIssues and PRs which have not yet been triaged by a lead

Status: Not planned (skipped).

#75017 In dotnet/roslyn;

· by michelemottini was closed on Sep 12, 2024