dotnet/roslyn

Move CLS compliance checking out of the compilers and into an analyzer

Open

#3,679 opened on Jun 24, 2015

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)C# (4,257 forks)batch import
Area-AnalyzersFeature RequestTenet-Performancehelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (PR metrics pending)

Description

CLS compliance checking is currently done in the Roslyn compilers (see https://github.com/dotnet/roslyn/search?q=ClsComplianceChecker). It should be moved out of the compilers and into a separate analyzer.

Contributor guide

Research direction
Extract the CLS compliance checking logic from the existing compiler code and create a separate analyzer project. Ensure the analyzer correctly identifies CLS compliance issues and integrates with the Roslyn analyzer infrastructure.
Tech stack
csharp
Domain
build systemtooling
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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#Roslyn APICode Analysis
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70