2 writes to MappedFileSpan
Microsoft.CodeAnalysis.Workspaces (2)
Diagnostics\DiagnosticDataLocation.cs (2)
73MappedFileSpan = new FileLinePositionSpan(GetNormalizedFilePath(unmappedFileSpan.Path, mappedSpan.Path), mappedSpan.Span); 77MappedFileSpan = mappedFileSpan ?? unmappedFileSpan;
8 references to MappedFileSpan
Microsoft.CodeAnalysis.Features (2)
EditAndContinue\EmitSolutionUpdateResults.cs (1)
68var fileSpan = SyntaxError.DataLocation.MappedFileSpan;
EditAndContinue\Utilities\Extensions.cs (1)
132var fileSpan = data.DataLocation.MappedFileSpan;
Microsoft.CodeAnalysis.LanguageServer.Protocol (3)
Features\EditAndContinue\EditAndContinueDiagnosticSource_OpenDocument.cs (2)
71var span = data.DataLocation.UnmappedFileSpan != data.DataLocation.MappedFileSpan ? data.DataLocation.MappedFileSpan.Span : default;
Handler\Diagnostics\DiagnosticsPullCache.cs (1)
116WriteFileLinePositionSpan(location.MappedFileSpan, writer);
Microsoft.CodeAnalysis.Workspaces (3)
Diagnostics\DiagnosticData.cs (1)
153=> $"{Id} {Severity} {Message} {ProjectId} {DataLocation.MappedFileSpan} [original: {DataLocation.UnmappedFileSpan}]";
Diagnostics\DiagnosticDataLocation.cs (2)
19/// diagnostic to a different file or location. Most clients should instead use <see cref="MappedFileSpan"/>, 101/// cref="UnmappedFileSpan"/> and <see cref="MappedFileSpan"/> corresponding to the respection locations of