Where to get feedback and contributors for a Rust language?

That’s a great kind of project to bring to the systems programming community. A systems language implemented in Rust can attract interest from compiler engineers, Rust developers, runtime and OS enthusiasts, and people who enjoy experimenting with new language designs. The key is to make it easy for people to understand what makes your language different, try it in a few minutes, and find a meaningful way to contribute. I’d approach this on two tracks: get substantive technical feedback on the language itself, and recruit early contributors by giving them a clear entry point. ## Where I’d look for feedback and contributors  1. [r/ProgrammingLanguages](https://www.reddit.com/r/ProgrammingLanguages/) Best for language-design feedback: type systems, syntax, memory models, compiler architecture, and what makes your language distinctive. Share a small code example and ask specific questions rather than simply announcing the project.  2. [r/rust](https://www.reddit.com/r/rust/) Good for finding Rust developers who might review your compiler implementation, suggest crates, investigate performance, or contribute code. Emphasize the engineering and implementation details.  3. [This Week in Rust](https://this-week-in-rust.org/) Look into its Call for Participation opportunities for ways to reach people interested in contributing to open-source Rust projects. [How to find small (and intermediate) open source projects to contribute to? - community](https://users.rust-lang.org/t/how-to-find-small-and-intermediate-open-source-projects-to-contribute-to/66044)[Rust open source project - community](https://users.rust-lang.org/t/rust-open-source-project/101602)  4. [Rust community forums and chat](https://rust-lang.org/community/) A useful route to broader systems-programming discussions, Rust user forums, community chat, and meetups. [Community](https://rust-lang.org/community/) ## What makes people want to contribute? For a systems language, I’d prioritize these things in your repository: - A compelling example: Show a small program in your language alongside the command to compile and run it. - A clear design rationale: Explain why someone would choose your language over Rust, C, C++, Zig, or Odin. Be specific about the trade-offs. - A quickstart that actually works: Installation, a minimal program, compiler invocation, and expected output. - A roadmap: Identify what's implemented, what's experimental, and what isn't supported yet. - Good first issues: Small, concrete tasks such as diagnostics improvements, parser tests, documentation, example programs, and bug fixes. - An explicit invitation to critique: Ask for reviews of the compiler architecture, memory safety guarantees, type-system design, and generated machine code where applicable. ## A post you can adapt Writing I've been building a systems programming language in Rust, and I'm looking for people interested in trying it out, reviewing the implementation, or contributing. The project is currently at [stage of development]. Its main goals are [two or three defining design goals], and it currently supports [key features]. I'd especially appreciate feedback on: - Language design and ergonomics - Compiler architecture and implementation - Performance and code generation - Missing features, bugs, and potential contributions Repository: [GitHub link] Documentation / examples: [link] Getting started: [instructions] The project is [open source / license], and contributions of all sizes are welcome. I'd love to hear what you think, including constructive criticism of the design and implementation. ## Let me help you get more targeted feedback What's the GitHub repository for your language? I'll take a look at the actual project and help you identify its strongest differentiators, areas that deserve technical review, and the best places to recruit contributors. I can also help sharpen your announcement so it attracts people interested in the language's particular design rather than just general encouragement.

**You’re in a great position - there’s real interest right now in Rust-inspired systems languages, and communities are open to contributing if you make your project visible and approachable.** To attract feedback and contributors, you’ll want to highlight your language’s unique design goals, provide clear documentation, and plug into existing Rust and systems programming communities. ## 🌟 Key Lessons from Similar Projects * **Rue(2026)**: A Rust contributor launched Rue, a systems language built with AI assistance, focusing on memory safety without Rust’s borrow checker. Rue gained attention because it clearly articulated its trade-offs (simpler ergonomics vs. reduced performance) and had active design documentation on GitHub. The Hacker News community engaged with Rue because it was positioned as filling a gap between Rust and garbage-collected languages[Rust Contributor Explores AI-Assisted Compiler Development with New Rue Language - InfoQ](https://www.infoq.com/news/2026/01/steve-klabnik-rue-language-ai/). * **Rust Itself**: The Rust project thrives because it has a strong contributor onboarding process - Zulip streams for new members, detailed dev guides, and a clear code of conduct. This lowers the barrier for new contributors[rust/CONTRIBUTING.md at main · rust-lang/rust · GitHub](https://github.com/rust-lang/rust/blob/main/CONTRIBUTING.md). ## 📋 Practical Steps for Your Language 1. **Clarify Your Vision** * What problem does your language solve better than Rust or C/C++? * Is it performance, ergonomics, safety, or tooling? * Contributors are more likely to join if they see a distinct niche. 2. **Open Source Infrastructure** * Host your repo on GitHub/GitLab with a clear `README`, roadmap, and contribution guidelines. * Provide examples of syntax and “killer features” that differentiate your language. 3. **Community Building** * Announce on Rust forums, Hacker News, Reddit’s r/rust, and systems programming Discords. * Consider writing a blog post or technical deep dive explaining your design choices (like Rue did). 4. **Onboarding Contributors** * Provide a “good first issue” list. * Document compiler architecture and language semantics. * Offer a Zulip/Discord channel for real-time discussion. ## ⚠️ Challenges to Anticipate * **Skepticism** : Many developers will ask why your language is needed when Rust already exists. Be ready with a clear answer. * **Complexity vs. Adoption**: If your language simplifies Rust’s borrow checker or adds new abstractions, you’ll need to prove it doesn’t compromise safety. * **Longevity** : Contributors want to know the project isn’t a short-lived experiment. A roadmap helps. ## ✅ Next Steps * Draft a blog post introducing your language, its goals, and a demo program. * Set up a GitHub repo with contribution guidelines modeled after Rust’s `CONTRIBUTING.md`. * Share your project in Rust and programming communities to gather early adopters. Would you like me to help you **draft a contributor call post** (like a Hacker News or Reddit announcement) that explains your language’s vision and invites feedback? That could be a strong way to kickstart visibility.

Building a systems programming language in Rust is a serious milestone. Whether you built a domain-specific scripting engine, an LLVM-backed compiled language, or an interpreted toy language, finding early contributors and actionable code review comes down to making your repository friction-free for newcomers. Here is a quick roadmap to gather feedback and recruit contributors, followed by a few ways we can work together right now. ## 1\. Where to Post for Feedback & Early Contributors * **Reddit:** * `r/Rust`: Frame it around _how_ you used Rust (e.g., "Built an LLVM frontend using `inkwell` in Rust - lessons learned and looking for feedback"). * `r/LanguageDesign`: Best place for feedback on syntax, type systems, and semantics. * `r/Compilers`: Best place for feedback on AST generation, IR design, type inference, and backend codegen. * **Discord Communities:** * **Rust Programming Language Discord** (`#project-showcase` or `#compiler-dev`). * **User Group Discord Channels** dedicated to compiler design and systems programming. * **Hacker News:** Submit as a **"Show HN"**. Focus the title on the core problem your language solves or its unique design philosophy (e.g., _Show HN: MyLang – A memory-safe systems language with explicit arena allocation_). * **Lobste.rs:** High-signal technical community (requires an invite, but worth posting if you have access). ## 2\. Essential Repo Checklist to Lower the Contribution Barrier Before sharing publicly, ensure your repository has these five elements: Element| What to Include ---|--- **Clear Pitch**| A 3-sentence explanation in the `README.md` explaining _why_ this language exists and what problem it addresses. **Quickstart Code**| A short, copy-pasteable example showing syntax, main features, and "Hello World". **Architecture Doc**| An `ARCHITECTURE.md` file outlining the pipeline: `Lexer → Parser → AST → Type Checker → IR/Codegen`. **"Good First Issues"**| Tag 3–5 small, isolated issues (e.g., "Add modulo operator", "Improve error formatting for missing semicolons"). **One-Step Build**| Running `cargo test` and `cargo run -- example.lang` should work out-of-the-box without obscure C/LLVM dependencies.

That is an incredible project! Building a systems programming language in Rust is no small feat - you're tackling everything from lexing and parsing to type-checking, LLVM/codegen (or your own backend), and memory management. To help you get the right eyes, feedback, and contributors on your project, here are the best places and strategies to share it: * * Community Platforms: Post your project on the r/rust subreddit (and r/ProgrammingLanguages), share a "Show HN" on Hacker News, and drop a link in the **#project-showcase** channel of the official Rust Discord or the Rust community forums. * Documentation & First Impressions: Make sure your `README.md` features a dead-simple "Hello World" example, a 60-second quickstart guide, and clear instructions on how to build and run the compiler from source. * Contributor Onboarding: Create a `CONTRIBUTING.md` file and label a few issues as **good first issue** or **help wanted** (e.g., parser edge cases, writing standard library stubs, or improving error messages) so new contributors know where they can jump in. * Design Architecture: Write a short design doc or architecture overview outlining your language goals (e.g., memory model, target audience, syntax inspirations) so potential contributors understand your vision at a glance. * If you'd like to share more, tell me: * What is the **name and core philosophy** of your language? * What **backend** does it use (LLVM, Cranelift, or your own)? * What kind of **feedback or contributors** are you looking for right now (language design, compiler perf, parser, docs)?

Post a concise project announcement on the Rust Users Forum with the repo link, what makes the language distinct, its current status, and specific feedback or contributor help you’re seeking. The forum’s announcements category is used for sharing Rust projects, and a recent language author sought code feedback there.([users.rust-lang.org][1])([users.rust-lang.org][2]) [1]: https://users.rust-lang.org/c/announcements/6?no_subcategories=false&page=4 "announcements - The Rust Programming Language Forum" [2]: https://users.rust-lang.org/t/feedback-for-a-language-written-in-rust/142100 "Feedback for a language written in Rust - code review"