dotnet/roslyn

In the VB sources, prefer the "Is" operator rather than Object.ReferenceEquals

Open

#2,150 建立於 2015年4月21日

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

描述

We generate slightly better code for the VB Is operator than we do for invocations of Object.ReferenceEquals. It would be nice to replaces uses of the latter with uses of the former.

貢獻者指南

技術棧
無
領域
backendperformance
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic VB syntaxRoslyn project structure
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Locate VB source files in the Roslyn repository, likely under src/Compilers/VisualBasic. Search for invocations of Object.ReferenceEquals and replace them with the VB 'Is' operator where semantically equivalent. Ensure the replacement is valid for reference type comparisons only. Since this issue is from 2015, verify that no existing PR or changes have addressed it. Review any comments for additional context.