The official repository for the design, proposal, and specification of the C# programming language.
C# Language Design is the official GitHub repository where the future of the C# programming language is shaped. It is the central location for proposing, discussing, and specifying new language features before they are implemented in the Roslyn compiler. It provides transparency into the design process and community collaboration that guides C#'s evolution.
C# language enthusiasts, compiler developers, and software engineers who want to propose, understand, or contribute to the design of new C# language features. It is also for teams building tools or libraries that need deep insight into upcoming language changes.
It offers direct, structured access to the language's design process and decision-making, allowing the community to participate in shaping C#'s future. Unlike informal forums, it provides an official, traceable pipeline from idea to specification, ensuring features are well-vetted and aligned with the language's goals.
The official repo for the design of the C# programming language
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The README details a formal championing and review process with design meetings, ensuring community input and structured language evolution.
Structured forums allow developers to propose and debate features, as emphasized in the Discussions section, fostering collaborative input.
Milestones like Working Set and Backlog signal prioritization, helping users track which proposals are actively considered for future releases.
Archives of design meetings and proposals in the meetings folder provide deep insight into the rationale behind language decisions.
The requirement for championing by LDT members and formal meetings can delay feature adoption, as noted in the design process with proposals potentially being postponed or rejected.
Proposals must be invited by champions, making it difficult for external contributors to directly influence design without prior engagement or approval.
Design and implementation are split between this repo and Roslyn, meaning approved features require additional work in a different repository to become usable.