ringabout

made a PR to nimsl https://github.com/yglukhov/nimsl/pull/8 ref https://github.com/nim-lang/Nim/issues/20016

made a PR to zero-functional => https://github.com/zero-functional/zero-functional/pull/77 ref https://github.com/nim-lang/Nim/issues/19795

made an issue for inim => https://github.com/jangko/nim-noise/issues/23

I have taken care of all important packages by creating issues or PRs except for arraymancer. I will be on it => https://github.com/nim-lang/Nim/pull/20070#issuecomment-1193958741

work on making arraymancer compatible with ORC => https://github.com/mratsim/Arraymancer/pull/573

Almost every failed important package is taken care of in one way or another. - [ ] nesm => https://github.com/xomachine/NESM/issues/21 - [x] iterutils => https://github.com/def-/nim-iterutils/pull/15 - [ ] cello =>...

Because the devel enabled `threads:on` by default. Closure iterators are much slower with `threads:on` in ARC/ORC. Use `threads:off` as an optimization for now.

I did a profile again  thread specific logic increase the time and mimalloc doesn't help this.

> This capture should be legal as it is a fresh local instance of the iterator. If this is true, this shall be a regression since 1.4.0 , https://github.com/nim-lang/Nim/commit/b022576ce96f5c166c7f5684bef9de682704cb1b looks...

> I seem to be running into pitfall after pitfall while trying to get the tests to run. Right now tests/misc/trunner_special.nim doesn't run in CI, seemingly due to some SSL...