extreme clang-tidy run times
Since MR !93 (merged) it seems our clang-tidy run times exploded (from 3 minutes to over 20 minutes), and it seems to be related to the backtrace implementation.
@jj, could you please check if there is something fishy going on? We also might to remove one or two of the clang-tidy rules (e.g. readability).