ShapeWorks coding style guide

[sheryjoe]

A document for development coding conventions (e.g. include with " vs <), naming, pragma once ... etc

[cchriste]

My favorite will be where to put the opening braces.

function(...) {
  ...
}

function(...)
{
  ...
}

(fwiw, these days I'm in favor of the first, on the same line; maybe we should vote)

Regardless of the current state, a coding standard will help us all move forward cohesively. The more I go over different modules created by different people, the more I both miss and appreciate consistency.

[akenmorris]

Probably best to start from something existing, for example:

https://google.github.io/styleguide/

For formatting, you can do "clang-format --style=google"

This can even be built into actions for PRs