Unifying code formatting about nnpops HOT 3 OPEN

One big commit is best, see https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view for how to make the web ui ignore the commit with blame (and how you can do the same locally)

from nnpops.

I think that we choose one of the existing formatting styles and adapt it (even if it needs reformating the existing code). For Python, it could be black. For C++, it could be LLVM.

from nnpops.

I am all in for adapting an established format. AFAIK when the option BasedOnStyle is not present, like in the above, the LLVM style is selected. So my config is LLVM except for what is present in those options.

Would a big commit reformatting all the code cause conflicts in existing pull requests or interfere with stuff like git blame?

from nnpops.