3 ms·
The problem with libc is twofold: first, reexports don't show up in the docs (bug on file [1]), and secondly, that every module gets a separate page (filed as [
by pcwalton 14y ago
The problem with libc is twofold: first, reexports don't show up in the docs (bug on file [1]), and secondly, that every module gets a separate page (filed as [2]). You can actually see the signatures for functions if you click through enough, e.g.
http://static.rust-lang.org/doc/0.6/core/libc_funcs_posix01_unistd___foreign_mod__.html http://static.rust-lang.org/doc/0.6/core/libc_funcs_posix01_...
Having to click through is annoying, though. It would be better to be able to specify that a module and all its submodules should go on one page in the docs.
Thanks for the bug report!
[1]: https://github.com/mozilla/rust/issues/3537 https://github.com/mozilla/rust/issues/3537
[2]: https://github.com/mozilla/rust/issues/5952 https://github.com/mozilla/rust/issues/5952
- eridius 14y agoMakes sense. Would fix the problem where I have no idea what prelude pulls in too. Also, part of my confusion with libc is that not all of the leaf modules actually have something in them. The first few I looked at were completely empty, so I thought the entirety of the libc documentation was empty.