A community-driven repository for proposing, discussing, and voting on future F# language and core library features.
F# Language Suggestions is the official community forum for proposing and shaping the future of the F# programming language and its standard library. It is a GitHub repository where users can submit ideas, discuss design trade-offs, and vote on potential new features, feeding into the language's formal RFC process.
F# developers, language enthusiasts, and contributors who want to influence the evolution of the F# language and core library by proposing or discussing new features.
It provides a structured, transparent, and community-driven channel for influencing F#'s development, governed by clear principles that prioritize language stability and coherence. It replaces an older uservoice system and integrates directly with the F# language design repository.
The place to make suggestions, discuss and vote on F# language and core library features
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Users vote via GitHub thumbs-up reactions on issues, providing a clear, transparent signal of community interest that helps prioritize features.
The decision-making factors and workflow are openly documented, with labels like 'approved-in-principle' showing progress, ensuring visibility into language evolution.
Suggestions move through labeled stages from proposal to completion, offering a predictable path from idea to potential implementation in the F# ecosystem.
Pre-filtered issue views (e.g., popular, newest, approved) make it easy to navigate hundreds of suggestions, saving time for contributors.
The emphasis on stability and gradual evolution means features take time to approve and implement, frustrating those seeking rapid innovation.
Votes are only an indicator; final decisions rest with a small design squad, which can diminish the perceived impact of community input.
Approved suggestions must go through a separate RFC process and require contributor ownership for implementation, adding layers of complexity.
Archived uservoice suggestions have broken comment links (404'ed), potentially losing valuable historical context for past decisions.