Janosch Müller

I think it would be only worth the effort to parallelize if it could be integrated into the normal spec run in a convenient way - not as a "spec...

> this tool does some relatively invasive rewriting of rspec methods [...] if I subtly break some rspec API I might invalidate your tests This could probably be avoided by...

> There is also the performance overhead which might be interesting to benchmark i did some [basic benchmarking](https://gist.github.com/jaynetics/3d8d0e5cfcbec3faf6412e0bd2b1adc4) because i was interested in this for my own project. i guess...

@cabo congratulations on your progress! it is an interesting project that i imagine could be of interest in more domains, not just jsonpath. a bit off-topic, but one quick thought...

if anyone else ends up here, i've released a fork, [omnibar2](https://www.npmjs.com/package/omnibar2), with react 18 as peer dep and some fixes.

i've made and still maintain the gem [delete_recursively]( https://github.com/jaynetics/delete_recursively ) which is based on `recurse-delete`. it works a little differently, though - you just add `dependent: :delete_recursively` to the assocation...

if anyone is still using this, i've release a forked gem, [`rubocop-git2`](https://github.com/jaynetics/rubocop-git2), with this and other fixes included

if anyone is still using this, i've release a forked gem, [`rubocop-git2`](https://github.com/jaynetics/rubocop-git2), with this and other fixes included

i've release a forked gem, rubocop-git2, with some fixes. i couldn't reproduce this particular issue, but if you encounter it, feel free to submit an issue at https://github.com/jaynetics/rubocop-git2/issues

see also #7287 which updates the documentation to reflect the standard-conforming behavior