I wanted to try and create a code analyzer and used the following Span<T> usage scenario as motivation:
Collapse AsSpan().Slice(start, length) into AsSpan(start, length)

This can be used to fix https://github.com/dotnet/corefx/issues/27330 (see dotnet/corefx#29078)

Screenshots:

Majority of the code here is template code. Focus on the following files:

• samples/SpanUsage/SpanUsage/SpanUsage/SpanUsageAnalyzer.cs
• samples/SpanUsage/SpanUsage/SpanUsage/SpanUsageCodeFixProvider.cs
• samples/SpanUsage/SpanUsage/SpanUsage.Test/SpanUsageUnitTests.cs

TODOs (I will file separate issues, and address outside this PR):

1. Add to corefxlab.sln (and build script to produce NuGet package and VSIX that get uploaded to MyGet) - Add to corefxlab.sln (and build script to produce NuGet package and VSIX that get uploaded to MyGet) #2212
2. Fix VSIX project to run using dotnet cli (via the command line) - Fix VSIX project so it can be built using dotnet cli (via the command line) #2213
   • Currently only builds in VS.
   • D:\GitHub\Fork\corefxlab\samples\SpanUsage\SpanUsage\SpanUsage.Vsix\SpanUsage.Vsix.csproj(94,3): error MSB4019: The imported project "D:\GitHub\Fork\corefxlab\dotnetcli\sdk\2.1.300-preview2-008530\Microsoft\VisualStudio\v15.0\VSSDK\Microsoft.VsSDK.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
3. Adjust the Diagnostic location to be more precise (currently highlights the parent tree, which ends up over highlighting whenever there are several method calls chained together). - Consider adjusting the diagnostic location to be more precise #2214
4. Update the VSIX description

Future code analysis rules that we can introduce:

• Memory<T>.Slice(...).Span => Memory<T>.Span.Slice(...) - Extend the SpanUsage code analyzer to check for Memory<T>.Slice(...).Span #2215

cc @dotnet/corefxlab-contrib, @tarekgh, @stephentoub, @atsushikan, @khellang, @VSadov, @KrzysztofCwalina