Project standard guideline

Hey everyone! How are you doing?

There is some really interesting code organization tips on Rust Book about separating responsibilities into different files for a binary and library crate.

As the good book says:

[...] the Rust community has developed a process to use as a guideline for splitting the separate concerns of a binary program when main starts getting large [...]

Maybe I did not search with the right words, but I only found this guideline at the book. So I wonder if there is a place standardizing the best practices for a given project code structure, not only syntax-wise, that Rust community agree upon.

It think it would be nice to have a place with guidelines for developing clean and straightforward projects.

What do you think?

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.