darkicewolf50/RustBrock
1
0
Fork 0
mirror of https://github.com/darkicewolf50/RustBrock.git synced 2025-06-14 20:44:17 -06:00
Code Issues Actions Packages Projects Releases Wiki Activity

started to edit down the baja stuff
Some checks failed
Test Gitea Actions / first (push) Successful in 12s
Details
Test Gitea Actions / check-code (push) Failing after 13s
Details
Test Gitea Actions / documentation-check (push) Has been skipped
Details
Test Gitea Actions / test (push) Has been skipped
Details

Browse Source
This commit is contained in:
darkicewolf50 2025-02-25 21:48:21 -07:00
parent f3ec0d98cc
commit 29f8753827
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
For later baja.md
View File

@ -5,7 +5,7 @@ You can learn more [here](https://doc.rust-lang.org/book/ch14-02-publishing-to-c
The goal of this is to passively train you how to produce comments and code worthy of being open source and industry level.
Due to the language's interesting module seperating when creating a large program. All members will be involved in the creation of all functions and how they should be seperated.
Due to the language's interesting module seperating when creating a large program. All members will be involved in the creation of all functions and how they should be seperated into their groups of related ideas.
First off the file tree structure will look like this example
```
@ -22,9 +22,10 @@ Where *`front_of_house.rs`* is like this
```rust
//! Describes what front_of_house module provides
//! All functionality in other files this serves as a connector
//! Main functionality or run should be a sub file named appropriatly
//! Main idea and a run should be in this file
//! re exports go here as well
pub mod a_different_mod;
// only split if a different losely related idea is needed (the sub idea more relates to itself than to the parent)
pub mod other_module_linked_in_modrs;
```
@ -63,6 +64,6 @@ pub fn example_funct(input_var: i32, b: i32) -> i32 {
}
```
One all of the main modules have been decided upon a senior member or lead will be assigned to that module will then be responsible and will break the module into sub modules with their team
One all of the main modules have been decided upon a senior member or lead will be assigned to that module will then be responsible and will break the module into sub components to assign out to implement.
The team will then come other for a final time to ensure that all modules and sub modules make sense and thier ideas make sense
The team will then come other for a final time to ensure that all sub modules make sense and thier ideas make sense and are appropriately assigned out.