Thread safety

Open chastell opened this issue 10 years ago • 3 comments

We’re currently not sure whether reek is thread-safe, but strongly suspect it isn’t (at least as long as we use Find.prune, but most probably in other places as well).

We should investigate whether we can make it thread-safe (and whether it’s worth it in the first place).

Jun 30 '15 04:06 chastell

I think this is worthwhile, being able to examine sources in separate threads could lead to big speed-ups on rubies with multi-processor support.

Jun 30 '15 06:06 mvz

I agree. Let's fix this. But this kind of implies to go through our complete codebase and check all-the-things, right?.:)

Jun 30 '15 20:06 troessner

Right, I don’t think there are any automated ways we could try to employ here… Did a cursory read of this piece and it seems to have the right ideas.

Jun 30 '15 22:06 chastell