> If you said "module X has no examples for action Y" this would've been an > actionable statement that can be turned into an issue for anyone to fix.
Well what I mean is that somebody learns Nim, they may struggle a lot to gather all the information necessary to be a really efficient developer with the language. The manual just summarize each part of the language. If you want to go further, all what you have is a list a procs with few lines of comment. That is very painful way to learn. Let's take an example, if I want to learn to use threads in Nim, all what the official doc give me as explanation is here: <https://nim-lang.org/docs/manual.html#threads>. It just takes three to four paragraphs. After that, I have to manage by myself to understand the modules `threads` and `threadpool`. It's not too hard to understand what each proc does, but to put all that together and really understand how parallel programming works in Nim... Few days ago, I opened a thread, on this forum just to ask about a detail in std/logging, because there was no explanation about it in the docs.
