Single-file CI and code style adoption

[brendan-nasa]

• An initial .clang-format¹ (ci script to follow)
• intent:
  • pick a style
  • stick to it for all new/modified code
  • trick approaches consistency with every merge :)
  • no more caring about how ugly/pretty your code is. run git clang-format before commit and be done with it
• Choice of BasedOnStyle is ultimately arbitrary, but current trick codebase matches WebKit style² closest³
• Code styles can be explored at https://clang-format-configurator.site/
• Only a bare minimum, first step to adopting more automated tooling (clang-tidy linter would be the next step)

Footnotes

1. its not allman, but it is a nice middle ground :) ↩

2. See WebKit's style guidelines for what's included ↩

3. alandefreitas/clang-unformat was run on trick repo and webkit resulted in least number of lines changed ↩

[coveralls]

Coverage is 55.991% — clang-format-proposal into master. No base build found for master.

[brendan-nasa]

placing this here for future reference

# clangd for vscode/zed/nvim
CompileFlags:
   Add:
      - -I<trick path>/trick/include
      - -I<trick path>/trick/share/trick

[brendan-nasa]

jeod already has a clang-format configuration¹ (maybe just adopt theirs after going over it)

existing clang-format configs in the nasa org can be viewed here: https://github.com/search?q=user%3Anasa+path%3Aclang-format&type=code&ref=advsearch

Footnotes

1. https://github.com/nasa/jeod/blob/main/.clang-format ↩

[brendan-nasa]

an example of integrating clang-format from an existing industry C/C++ codebase:
https://gitlab.com/AOMediaCodec/avm/-/tree/research-v13.0.0?ref_type=tags#coding-style