dotnet/roslyn

Investigate and fix/document the behavior when compiler is supplied with a netmodule reference in wrong casing.

Open

#1,672 建立於 2015年3月30日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)C# (20,414 star) (4,257 fork)batch import
Area-CompilersConcept-PortabilityDocumentationLanguage-C#Language-VBhelp wanted

描述

We had reports that some versions of CSC could embed two module references in the metadata - one as supplied and another matching the actual file name.

There should be just one module reference in the metadata.

貢獻者指南

技術棧
csharp
領域
tooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
C# programmingcompiler fundamentalsfamiliarity with .NET metadata
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
10
研究方向
Investigate the behavior of the C# compiler when a netmodule reference is supplied with wrong casing. Look at the metadata emission code in the Roslyn compiler, possibly in the Microsoft.CodeAnalysis.CSharp namespace. Write a unit test that supplies a netmodule reference with different casing and verify that only one module reference appears in the emitted metadata. Check if there are existing tests for module references. The issue may require understanding how the compiler resolves and embeds module references.