Timothee Cour

> I don't see the benefit in There is plenty of evidence pointing to the opposite, see the re-implementations and form posts I've linked. It is also my experience that...

can we at least agree on `compiler/`, `tools/` and anything except koch and stdlib can import fusion? Note that a recursive dependency between fusion and std doesn't imply cyclic module...

> @Yardanico nim-lang.github.io/Nim/globs.html this is from lib/std/private/globs.nim which I had added in https://github.com/nim-lang/Nim/pull/14501 for kochdocs, it's in private hence not intended for public use, just like `since`, etc. nim docs...

ping @Araq ; generally useful and would help with things like nimgrep (eg https://github.com/nim-lang/Nim/pull/15962#issuecomment-727086184) which now has to change to slightly slower closure iterators to avoid code bloat from multiple...

PTAL, rebased for conflict bitrot

replying to @araq https://github.com/nim-lang/Nim/pull/16709#issuecomment-762416829 > What I dislike about your walkPathsOpt is the callbacks, iterators that require callbacks are alien. there is precedent in stdlib, eg sequtils.filter: `iterator filter*[T](s: openArray[T],...

> So... how this is going ?. @Araq this should be moved back to a PR against stdlib (as was intially the case refs https://github.com/nim-lang/Nim/pull/15598). This is 100% stdlib territory,...

just replying on this point for now, will followup with other points later: > It's also not clear to me why "sorting" is important because it's easy to support efficiently...

* `doAssert(res) # res == -1` => you mean res == false * can you check whether it returns false directly here: ```nim when not defined(nimInheritHandles) and declared(setInheritable): let oshandle...

hit this again: ```nim block: # nim --eval let opt = "--hints:off" check fmt"""{nim} {opt} --eval:"echo defined(nimscript)"""".execCmdEx == ("true\n", 0) check fmt"""{nim} r {opt} --eval:"echo defined(c)"""".execCmdEx == ("true\n", 0) check...