3 As an organization we maintain a styleguide
[fn:1] which lists all of
4 the style guidelines we use for our code. If you are contributing to
5 one of our projects, you should review and understand the relevant
8 You should also review the
[[file:ulang.org][ulang]] document, which may shine some light
9 on code comments and developer docs.
11 [fn:1] https:
//google.github.io/styleguide/ 21 - start every source-file with a header comment
22 - use outline headings to organize your program
23 - use ulang-comments as needed for referencing bugs, notes, etc.
24 - inline documentation should be declarative. your code explains your
29 - prefer symbol docs to comment docs
34 - don't make
=mod.rs= files
35 - use the
=foo.rs=,
=foo/*= pattern instead
