But @Araq, many of Nim's commonly used packages aren't documented at all- and I can tell that the ones that are fall short in very important areas.
* They don't state in a nutshell what the package does, and when it should be used * They don't tell you how to get started, and if they do, they certainly don't tell you how to move forward * There is absolutely never any discussions of gotchas, subtleties and implications Compare this with- off the top of my head, pytest. On the first page, in the first paragraph, it says how to start your project. Now you know that. In the second paragraph, there are links to 30 how-to guides that cover different subjects, 5 reference guides that go over details, and five guides full of best practices and helpful gotchas. Now pick any other package and the results will not be that different. If I go look up the testament docs- by Nim standards they're not bad. But it starts with the gory details of configuring testament, states they are incomplete, and contains only two test cases. Following are only five examples, and you don't bother to speak to the reader in full sentences such as: You may place these tests into files and they will be run. That's it- now, sink or swim. It's not even close- or close to being close.
