Yeah, I think we should probably just re-format the whole code base and then fail the build if clang-format fails. Spending contributor or reviewer time on code formatting is silly. I just haven't had the time to come up with a clang-format settings file that minimises churn, since OSARA doesn't currently use one of the common styles, so we'll need to customise it a bit to avoid changing literally the entire code base. It'll also break any open pull requests, so we should try to get the ones we care about closed and kill the rest before we do it.

I'd also ideally like to normalise some stuff with clang-tidy like braces for all condition blocks, nullptr instead of NULL, etc.