Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
lwm1986
roslyn
提交
3993e8dd
R
roslyn
项目概览
lwm1986
/
roslyn
与 Fork 源项目一致
从无法访问的项目Fork
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
R
roslyn
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
3993e8dd
编写于
8月 09, 2018
作者:
C
Cyrus Najmabadi
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Make readonly. Add docs.
上级
059a8a64
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
26 addition
and
9 deletion
+26
-9
src/Workspaces/Core/Portable/FindSymbols/FindReferences/Finders/FinderLocation.cs
...able/FindSymbols/FindReferences/Finders/FinderLocation.cs
+20
-3
src/Workspaces/Core/Portable/FindSymbols/FindReferences/Finders/NamedTypeSymbolReferenceFinder.cs
.../FindReferences/Finders/NamedTypeSymbolReferenceFinder.cs
+6
-6
未找到文件。
src/Workspaces/Core/Portable/FindSymbols/FindReferences/Finders/FinderLocation.cs
浏览文件 @
3993e8dd
...
...
@@ -3,10 +3,27 @@
namespace
Microsoft.CodeAnalysis.FindSymbols.Finders
{
internal
struct
FinderLocation
internal
readonly
struct
FinderLocation
{
public
SyntaxNode
Node
;
public
ReferenceLocation
Location
;
/// <summary>
/// The actual node that we found the reference on. Normally the 'Name' portion
/// of any piece of syntax. Might also be something like a 'foreach' statement node
/// when finding results for something like GetEnumerator.
/// </summary>
public
readonly
SyntaxNode
Node
;
/// <summary>
/// The location we want want to return through the FindRefs API. The location contains
/// additional information (like if this was a Write, or if it was Implicit). This value
/// also has a <see cref="ReferenceLocation.Location"/> property. Importantly, this value
/// is not necessarily the same location you would get by calling <see cref="Node"/>.<see
/// cref="SyntaxNode.GetLocation"/>. Instead, this location is where we want to navigate
/// the user to. A case where this can be different is with an indexer reference. The <see
/// cref="Node"/> will be the node for the full 'ElementAccessExpression', whereas the
/// location we will take the user to will be the zero-length position immediately preceding
/// the `[` character.
/// </summary>
public
readonly
ReferenceLocation
Location
;
public
FinderLocation
(
SyntaxNode
node
,
ReferenceLocation
location
)
{
...
...
src/Workspaces/Core/Portable/FindSymbols/FindReferences/Finders/NamedTypeSymbolReferenceFinder.cs
浏览文件 @
3993e8dd
...
...
@@ -110,17 +110,17 @@ protected override bool CanFind(INamedTypeSymbol symbol)
}
var
result
=
ArrayBuilder
<
FinderLocation
>.
GetInstance
();
foreach
(
var
reference
in
namedTypeReferences
)
foreach
(
var
finderLocation
in
namedTypeReferences
)
{
if
(
Contains
(
constructorReferences
,
reference
))
if
(
Contains
(
constructorReferences
,
finderLocation
))
{
var
loca
lReference
=
reference
;
loca
lReference
.
Loca
tion
.
IsDuplicateReferenceLocation
=
true
;
result
.
Add
(
localReference
);
var
loca
tion
=
finderLocation
.
Location
;
location
.
IsDuplicateReferenceLocation
=
true
;
result
.
Add
(
finderLocation
);
}
else
{
result
.
Add
(
reference
);
result
.
Add
(
finderLocation
);
}
}
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录