suggestion: note about Cargo.lock and git about cheats.rs

[ralfbiedert]

Hm, I'm not sure where to add this. It's too little for it's own section, but it doesn't seem to fit anywhere else.

A thought that crossed my mind was adding a "Project Anatomy" section explaining what goes where, but I'm not sure if that isn't already solved for most people by just using the standard tools.

[ralfbiedert]

Note to self:

If there is a (project) anatomy section, maybe it should also have absolute MVP examples how a benchmark and unit test have to look like.

After all these years, I still don't manage to write a benchmark from scratch w/o having to look up how I did it the previous time ...

[yaahc]

You're the freaking best. Ty for doing this!

[kud1ing]

Nice. What would you think about linking Cargo in this section to https://cheats.rs/#tooling instead of https://doc.rust-lang.org/cargo/index.html ? This way, people could stay in cheat sheet land longer.

[kud1ing]

Maybe in https://cheats.rs/#tooling which is about cargo?

[ralfbiedert]

Maybe in https://cheats.rs/#tooling which is about cargo?

Tooling so far is about using existing tools. I think it would look a bit out-of-place just talking about these two files there.

Generally, adding them just for the sake of avoiding Git mistakes sets the bar too low IMO (it's not a mental blocker, in most cases it has no consequences and it can easily be fixed), which is why I would prefer mixing that information into a bigger section; however one that is a about files / project layout or something similar.

Then, however, comes the question, is that section actually needed / wanted?

[ralfbiedert]

Project anatomy section created. Feel free to reopen / comment.

[ralfbiedert]

Good idea, thanks.