dotnet/csharplang

The official repo for the design of the C# programming language

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 31 minutes ago
Added to GitGenius on September 4th, 2026
Created on December 9th, 2016
Open Issues & Pull Requests: 289 (+0)
GitHub issues: Enabled
Number of forks: 1,079
Total Stargazers: 12,697 (+0)
Total Subscribers: 678 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 226
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,566 days
Stale 30+ days: 207
Stale 90+ days: 187

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 1

Top labels

  • Proposal champion (362)
  • Implemented Needs ECMA Spec (132)
  • Proposal (130)
  • Feature Request (27)
  • Smallish Feature (22)
  • untriaged (21)
  • standard proposal (17)
  • Design Review (15)

Most active issues this week

Detailed Description

The C# Language Design repository is the official venue where new features for the C# programming language are developed, adopted, and formally specified.

The repository addresses the need for a transparent, structured process to evolve the C# language. It serves as the central hub where language design decisions are made through a coordinated effort between the Language Design Team and the Roslyn compiler project. The design process begins with community discussions, moves through championing by team members, proceeds to Language Design Meetings, and culminates in formal proposals and specifications. Active proposals are maintained in a dedicated folder alongside meeting notes and language version history.

Developers and language enthusiasts should use this repository if they want to participate in shaping C# or understand how language features are designed and adopted. It is suited for anyone proposing new language features, reviewing active proposals, or tracking the rationale behind language decisions. The repository emphasizes that new feature proposals should first be raised as discussions rather than submitted directly as issues or pull requests; only members of the Language Design Team can champion proposals for formal consideration. The design process documentation provides the complete framework for how ideas move from discussion to adoption.

The project maintains active engagement with the community through structured discussions that are moderated to stay on topic and remain navigable. Language Design Meetings occur regularly and inform the evolution of proposals. The repository accepts bug reports and pull requests for corrections to existing documentation and specifications. The team enforces clear guidelines for discussions to ensure they remain focused and useful, and it locks champion issues to consolidate discussion in linked discussion threads rather than spreading conversation across multiple locations.