-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Description
Summary
Looking at the index, there are quite a few modules that are not linked from the main stdlib documentation (https://nim-lang.github.io/Nim/lib.html):
Most of them seem to be internal/experimental/unstable (note that some unstable modules are nevertheless linked), but some look like they should be linked from the main stdlib documentation page, for example:
- assertions
- atomics (added more modules to docs lib #17430)
* [] channels - enumerate (added more modules to docs lib #17430)
- io
- jsbigints
- jsonutils (added more modules to docs lib #17430)
- nre
- packedsets (Improve documentation for packedsets #16715)
- parsejson (added more modules to docs lib #17430)
- rdstdin (added more modules to docs lib #17430)
- setutils (Add std/setutils to lib.rst #16791)
- tempfiles (Add link to std/tempfiles in the docs; fix #19155 #19807)
- with (added more modules to docs lib #17430)
- std/exitprocs
Is there a reason they aren't linked? Are there more modules that should be linked? And perhaps there are some modules that are currently linked, but shouldn't be (like intsets)?
Related issue: #16046.
Possible solution
I'd be willing to create a PR to link all the missing modules.
As mentioned in the linked issue, while generating the documentation, one could automatically check that all modules are linked. For modules that are not supposed to be linked (internal, experimental, deprecated or unstable modules), there could be a way (a pragma or a special comment?) to mark them as such. Alternatively, they could be linked in a separate section ("Internal modules").