Open mavasani opened 6 years ago
dotnet/roslyn-analyzers#2395 raises another false positive from IOperation analyzer in presence of XML syntax nodes (XmlElement in the provided repro). We drop the entire tree under XmlElement leading to false positives from unused parameter analyzer. We may want to prioritize this issue to ensure we are not dropping child operations in presence of VB XmlXXX syntax nodes.
Tagging @dotnet/analyzer-ioperation @AlekseyTs @333fred @jinujoseph @KathleenDollard
Seems like we are dropping lot of xml related bound nodes for VB in the operation tree. Attempting to add them with this commit caused failures down the line where we have multiple explicit operation nodes with same syntax. Fixing that issue uncovered presence of cycles in the bound tree where same bound node appears at multiple places in the bound tree, leading to asserts.
Note that whenever we fix this issue, we also need to uncomment an assert in ControlFlowGraphBuilder and add relevant CFG unit test(s).