dotnet/runtime

[ILVerify] Add optional warnings for constructs that are likely incorrect

Open

#37,390 opened on May 11, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C# (5,445 forks)batch import
Priority:2area-Tools-ILVerificationhelp wanted

Repository metrics

Stars
 (17,886 stars)
PR merge metrics
 (Avg merge 12d 11h) (661 merged PRs in 30d)

Description

  • Catching exception that does not derive from System.Exception
  • location that immediately follows an unconditional branch, and not a target of an earlier branch instruction, then the state of the evaluation stack at X must be empty.

Contributor guide

Research direction
Study ILVerify codebase to understand where to add warnings for catching non Exception and unreachable code after unconditional branches.
Tech stack
csharp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30