While excess can be bad, and there are inconsistencies that should be repaired, I think a "batteries included" stdlib is a good thing. E.g., the recent `enumerate` for loop macro in `tests/macros/tforloop_macro1.nim` should probably be in `lib/pure/sugar.nim`. I think the duplication (`re` and `nre`, `parseopt` and `parseopt2`) should go. `mersenne` does seem pointless. Maybe game programmers use `basic[23]d`? I think `coro` is a good example of low level programming in Nim, but I don't know if needs to be in the stdlib.
I like `set[]`, "do", converters, and exceptions. Exception-free alternatives in the stdlib sounds good, though. I think `using` is a good idea. I don't usually use dynamic dispatch of any kind, but the Lisp world swears by multi-methods for such and they are more general than the usual first-slot-only OO dispatch. No opinion on holey enums vs distinct ints or `discardable`. I never liked non-case-sensitivity or `TaintedString`. I think it would be nice if `openArray` could be more "open". It could become a first class `concept` needing only `[]`, `len`, etc. when concepts are ready enough. That may be already planned.
