dotnet/roslyn

Incorrect behavior when using alias refers to namespace in using alias

Open

#1,027 创建于 2015年3月4日

在 GitHub 查看
 (17 评论) (1 反应) (0 负责人)C# (20,414 star) (4,257 fork)batch import
Area-CompilersBughelp wanted

描述

extern alias Contracts1;
extern alias Contracts2;

using alias1 = Contracts1::TestContractAssembly;
using alias2 = Contracts2::TestContractAssembly;

partial class Contract : alias1.IContract, alias2.IContract
{
    int alias1.IContract.x
    {
        get
        {
            return 1;
        }
    }
    int alias2.IContract.x
    {
        get
        {
            return 1;
        }
    }
}

Both IContract types are the same - they expose an int property "x". Roslyn incorrectly reports that IContract.x has already been implemented.

This works if you inline the using aliases.

I strongly suspect that the alias points to the merged namespace symbol, rather than to the namespace symbol contained in the assembly symbol referenced by the extern alias.

贡献者指南

技术栈
csharp
领域
tooling
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
5
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
needs maintainer response
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
C#Roslyn compiler internalsunderstanding of extern aliases
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
10
研究方向
Investigate the Roslyn source code related to namespace alias resolution. The issue suggests that alias references are incorrectly resolved to merged namespace symbols instead of assembly specific ones. Look at the SemanticModel or symbol resolution logic, likely in files like `Symbol.cs` or `NamespaceSymbol.cs`. Review comments in the issue for any suggested code paths. A fix would require ensuring that extern alias references maintain proper assembly boundaries when resolving namespaces.
Incorrect behavior when using alias refers to namespace in using alias · dotnet/roslyn#1027 | Good First Issue