Thanks for submitting this. It's good to see different approaches.

I see. It also looks like "run_order" was switched to llvm_project_revision for some reason (I couldn't quite get why - is it simply because the old schema used it? Seems not worth it even if it's hard to correct it in LNT), but if it won't change the behavior (i.e. produced reports) for existing LNT users then it's fine. There seems to be some confusion around what run order is supposed to be already.

What does this mean for the existing v1 users? Will they continue using v1 format, i.e. will LNT keep using whatever it was using before this patch or will it switch to v2? Btw, is there some place/short summary of the rationale behind v2? Not really related to this patch per se, just want to understand the implication of the new format for the downstream users.

Any particular reason this was never followed through? This pass might solve https://bugs.llvm.org/show_bug.cgi?id=42965 .

ping

How big is the slowdown?

Would that also skip checks for something like shared_ptr?

ping

Would it make clang-format linker available to Phabricator automatically or it would still be required to be run manually by those submitting the diffs?

I'm also using pycodestyle 2.4.0. The error/warning was not about raw strings in regexps, rather illegal escape sequences, i.e.:

@kristof.beyls Thanks. Yes, I don't have commit access as I indicated in my previous reply (unless I was somehow given one without my knowledge). I'd be happy if you could commit this on my behalf.

@MatzeB ping

@MatzeB Is there something else I should do for this to be commited? First time using the Phabricator so I'm a bit unfamiliar with the process.

In D45000#1078268, @MatzeB wrote:

Tgiugh this is another sign that the global_status view probably isn‘t used byanyone ans has no tests. I still think we should just remove it...

ping

I see no changes between Diff 143597 and Diff 143602.