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.