The style guide is to run cargo fmt. The default rustfmt configuration is good enough. Code should also pass cargo clippy without warnings. Some projects define a just check/just check-json recipe that runs cargo clippy --all-features -- -W clippy::pedantic to catch a plethora of additional suggestions from clippy that are disabled by default. Basic warnings about integer conversions can be annotated to allow them.
this post was submitted on 09 Jul 2023
8 points (100.0% liked)
Pop!_OS (Linux)
5143 readers
5 users here now
Pop!_OS is an operating system developed by System76 for STEM and creative professionals who use their computer as a tool to discover and create. Unleash your potential on secure, reliable open source software. Based on your exceptional curiosity, we sense you have a lot of it.
Whether this is your first experience with Linux, or your latest adventure, all are welcome to discuss and ask questions about Pop!_OS and COSMIC. Keep the discussions friendly though, and remember to assume good intentions whenever you reply. We're all here because we have a shared love for Linux and open source software.
Support us by buying System76 hardware for you or your company! Or by donating on the Pop!_OS website through the "Support Pop" button. Pop!_OS and COSMIC are fully funded by System76 hardware sales. All systems are assembled in the USA. With your support, we'll work to push the Linux desktop forward with COSMIC.
Links
Guides
Hardware
Recommended
- !system76@lemmy.world
- !linux@lemmy.ml
- !opensource@lemmy.ml
- !linux@programming.dev
- !linux_gaming@lemmy.world
- !linux_gaming@lemmy.ml
- !selfhosted@lemmy.world
- !rust@programming.dev
- programming.dev
- fosstodon.org (Mastodon)
- !redox@lemmy.world
Community Rules
Follow the Code of Conduct
All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct
Be helpful
Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like "RTM" or links to LMGTFY. Linking to direct sources that answer the asker's question is fine, but it's advised to provide some explanation as to how you got to that source.
Critique should be constructive
We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic "It's bad" or other simple negative comments don't help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.
This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.
Don't post malicious "advice"
It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.
Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn't serious, but a new user might not.
No personal attacks
Posts making a personal attack on any user will not be tolerated.
No hate speech
Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.
founded 1 year ago
MODERATORS
thank you
Do you mean framework?
No I mean something like this.
What Rust's maintainers recommend is what I'd recommend: https://rust-lang.github.io/api-guidelines/
Many of these are automatically detected and suggested by clippy's pedantic flag.
Thanks
view more: next ›