Zak Cutner

Hello @sgowroji! This could be reproduced on any Bazel project that builds some C/C++ code, on a system with `-debugger-tuning=lldb` set (I'm not sure what causes this to be set...

Thanks @keith! I just tested your branch and it works great 😄

Hello, thanks for bringing this up! These methods are unsafe since they are annotated with `target_feature(enable = "avx2")` although hopefully that [may not be required soon](https://rust-lang.github.io/rfcs/2396-target-feature-1.1.html). I can add a...

That's a really great idea, thanks 👍 We'll probably change around the API a bit at some point (we'd like to support SSE2 without AVX2 for example) so we can...

@quasilyte @cristaloleg Sorry for the ping, I just wanted to ask if either of you might get a chance to take a look at this please?

@cristaloleg Unfortunately, I don't think I can share the stack trace dump of all goroutines, since this is from a private project, but here is the trace from the goroutine...

@quasilyte Thanks for taking a look at this! > If writes happen at these times, it means that the app itself doesn't synchronize the read/write operations. If I'm understanding correctly,...

Thanks for the helpful explanations, I think I understand this better now. I'm using the `go/analysis` integration (through nogo), which I think might not adhere to this since the context...

> Yes, that's because every instantiated checker is expected to be run on a dedicated goroutine. Ah, I see! So the `go/analysis` integration will also need to be updated to...

Makes sense! Would you be opposed to a PR to the `go/analysis` implementation in this project under [`checkers/analyzer`](https://github.com/go-critic/go-critic/tree/master/checkers/analyzer), to make it behave more like the one in golangci-lint? It's of...