Unify Coding Conventions

[CL16gtgh]

• Define macros vs. const variables
• Pointer vs. reference handles
  • e.g. Steering system (currently owns reference to primary sensor)
• CAN send and receive functions in different interfaces concerned
  • Implementation details might vary, but might be a good idea to "look" the same when being dispatched in main
  • e.g. Inverters, MCU, and Dashboard interface
• CAN bus handling in main/HyTechCANInterface
  • Periodic/asynchronous send

[walkermburns]

To expand on this: we need to comb through the codebase and decide on similar naming schemes for functions and variables just to improve readability.

This is most noticeable with our CAN read and write functions, some interfaces use read and write, others use get and enqueue, this should ideally all be the same. Another example is with ticking functions, the function names should include the tick frequency for the eventuality that multiple parts of the same interfaced are ticked at different rates.

This can be part of a cleanup effort after we have stabilized the code functionality.