🚀 Kick-off: Shaping the Rust Code Style Manifest

[RAprogramm]

🚀 Kick-off: Shaping the Rust Code Style Manifest

Hey everyone,

This is the very first discussion for RustManifest. The goal here is to create a living, collaborative document that defines how we write Rust code as a team and as a community.

The initial version of the style guide covers:

• Formatting with nightly rustfmt
• Consistent .rustfmt.toml configuration
• Naming conventions
• Code quality and best practices
• Branch management strategy
• Avoiding panics in production

---

💬 Feedback wanted

I’d love to hear your thoughts on:

1. Are the formatting rules strict enough, or do we need more flexibility?
2. Should we expand the guide with real-world examples and anti-patterns?
3. Any must-have conventions you’ve found useful in your own projects?

---

The idea is to keep this guide practical, readable, and production-focused.
No bikeshedding, but thoughtful improvements are welcome.

Looking forward to your input — let’s make this a solid reference for anyone contributing Rust code here.