-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modules not linked in the main stdlib documentation #16656
Comments
io and assertions are submodules of the system module |
I'm aware, but so are channels and threads, or are these different (other than only being available with |
Send PR maybe... |
There's quite a lot of modules that are nowhere to be found in https://nim-lang.github.io/Nim/lib.html, for example quite a lot of modules from https://github.com/nim-lang/Nim/tree/devel/lib/std |
I noticed rdstdin was missing |
Also missing: |
@locriacyber it's linked here: https://nim-lang.github.io/Nim/lib.html#wrappers-unix-specific. |
Not searchable, not in "The Index" in 1.6.4. Try searching "fork". |
That's not what this issue is about though (it's about modules linked from https://nim-lang.github.io/Nim/lib.html). The index apparently not including the |
It's not a bug, we want the index to contain useful information and not the Posix API. You're not supposed to use the Posix APIs unless you know what you're doing and in that case, you don't need the index. |
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:
* [] channelsIs 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").
The text was updated successfully, but these errors were encountered: