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