This is valuable data. When creating my [proposal](https://forum.nim-lang.org/t/3772/5), I manually inspected all Rosetta Code Nim solutions and got very similar results. The top five modules where:
* strutils * math * os * sequtils * times Of course data from real applications is still scarce. For example, _logging_ and _unittest_ should rank very high in reality. * * * Anyone demanding an all-batteries-included-stdlib for Nim 1.0 release should consider the enormous amount effort needed for reaching and maintaining production-ready quality. Below are some examples. I don't see why Nim could be the exception. [C (sample)](https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=string/tester.c) Boost: * [Boost.Test](https://www.boost.org/doc/libs/1_67_0/libs/test/doc/html/index.html) * [Conformance status](https://www.boost.org/doc/libs/1_67_0/doc/html/thread/compliance.html) Python: * [doc](https://docs.python.org/3/library/test.html) * [code](https://hg.python.org/cpython/file/tip/Lib/test) [Rust](https://brson.github.io/2017/07/10/how-rust-is-tested) Java: * [JCK](http://openjdk.java.net/groups/conformance/JckAccess/) * [JDTS](https://en.wikipedia.org/wiki/Java_Device_Test_Suite) * [SigTest](https://docs.oracle.com/javame/test-tools/sigtest/2_2/sigtest2_2_usersguide.pdf) [Javascript](https://github.com/tc39/test262)
