Izaak "Zaak" Beekman

@rweed Thanks for the suggestion! I agree, and have been using PSBLAS in a number of projects for work. I added the suggestion to the list of prior art at...

Also, I'm not really sure where this class of sparse linear-algebra routines would belong, but I often see very large tridiagonal, and pentadiagonal systems. To my (admittedly limited) knowledge, there...

@certik good idea. Do you happen to know the name of the Lapack procedure for diagonal matrices? I remember looking for a good serial implementation too and not finding it,...

Yes, I generally agree but for assertion-y stuff I think separating the verb with an underscore makes sense `is_alpha`. The legibility is much improved and client code can always consume...

## Automation of pedantry I think that we should also adopt solutions like [Editorconfig](https://editorconfig.org/), possibly [findent](https://www.ratrabbit.nl/ratrabbit/content/findent/introduction) [cmake-format](https://cmake-format.readthedocs.io/en/latest/) (if we use CMake) and clang-format (for any C code). Tools like these...

I agree, and for the record, I wasn't suggesting we pick whatever and let people rename through use association; Good names from the get-go are important.

Can we make some choices about indentation and tabs vs spaces? My preference is indent all indent-able things by two spaces; never use tabs. We can codify this in an...

A quick note: I'm happy with 2 or 4 but with the 132 character line limit, you can start to run out of real estate pretty quickly with 4 spaces.

80 characters per line and 4 spaces?! That seems like there will be an awful lot of line continuations and leading blanks... `findent` defaults to 2 spaces. The standard caps...

OK, let's go with 4 then, and we could admonish users to be within 80 characters (or 100, or whatever) but enforce a hard limit of 132 during CI. I'm...