-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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.
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
User Story: .NET 6.0 developers can verify more APIs for their correct usage to speed up their development #43617
Labels
area-Meta
Cost:XL
Work that requires one engineer more than 4 weeks
Priority:1
Work that is critical for the release, but we could probably ship without
Team:Libraries
User Story
A single user-facing feature. Can be grouped under an epic.
Milestone
Comments
11 tasks
cc @jeffhandley |
@jeffhandley A nice list of analyzers done for 6.0. Is there more to do here for 6.0 or shall we move to 7.0? |
I'd like to keep this in 6.0.0 until @mahdiva's assigned analyzers are completed, and the others in progress are captured with their final 6.0.0 status. Thereafter, I'll move this to 7.0.0 for the remainder. |
Closed
18 tasks
Minor correction; #40579 might also land in .NET 6.0 (RC2). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-Meta
Cost:XL
Work that requires one engineer more than 4 weeks
Priority:1
Work that is critical for the release, but we could probably ship without
Team:Libraries
User Story
A single user-facing feature. Can be grouped under an epic.
In .NET 5, we shipped approximately 250 analyzers with the .NET SDK. Many of them already existed but were shipped out-of-band as NuGet packages. Now, .NET comes with an in-depth code analysis and code fixer experiences. This means developers don't have to purely rely on their choices based on reading code completion; .NET can help them pro-actively identify when their code has issues, right from the start. However, many of the code analyzers created don’t come with code fixers yet. We will look at telemetry and customer feedback to prioritize (around a TBD set of principles) which code analyzers would most benefit from code fixers along with which are most popular and consider adding fixers for those. Also, there is a sizable backlog of code analyzers that didn't get included in .NET 5, which will need to prioritized and considered. Furthermore, our goal for .NET 6 is that new features in .NET 6 should come with analyzers.
Work Items
The getting started guide should be referenced for the Definition of Done to be used for each issue.
External contributors: If you'd like to work on one of the issues marked as "up for grabs", please add a comment directly on that issue asking to get it assigned to you, and tag @carlossanlop or @buyaa-n.
Buffer.BlockCopy
string.Concat
string.AsSpan()
overstring.Substring()
when parsingStream.ReadAsync/WriteAsync
Task.WhenAll
with a single argumentTask.WaitAll
with a single argumentDictionary<,>.Keys.Contains
withContainsKey
Environment.ProcessPath
Environment.CurrentManagedThreadId
String.Equals
instead ofString.Compare
SafeHandle
String.Contains(char)
instead ofString.Contains(String)
Work Items Not Completed in .NET 6.0
Thread.VolatileRead
andThread.VolatileWrite
analyzerAsParallel()
correctlyOfType<T>()
with impossible typesDictionary<K, V>.Remove(key)
byContainsKey(key)
Dictionary<K, V>.TryGetValue()
over guarded indexer accessDictionary<K, V>.TryAddValue(key)
over guardedAdd(key)
ExactSpelling=true
on[DllImport]
for known APIsHashData
methods overComputeHash
The text was updated successfully, but these errors were encountered: