3 ms·
I have no problem with the community helping to shape the language. But I think the difficulty in getting started with the language, due primarily to documentat
by eridius 14y ago
I have no problem with the community helping to shape the language. But I think the difficulty in getting started with the language, due primarily to documentation problems and lack of good introductory material, is going to make it harder for people to get involved.
I know when Go was first released I immediately jumped in and started using the language. I was even the first non-google, non-@golang person to get their name in the CONTRIBUTORS list (because I wanted to modify the emacs go-mode, but still). But I feel like I can't even get started with Rust because I have no idea what I'm doing and the documentation isn't helping.
For example, right now I'm trying to whip up a really tiny program to test out the FFI. But the libc module's documentation is completely nonexistent. It's just a series of nested modules, which end up having nothing in them. I'm sure there's actually stuff in the modules, otherwise they wouldn't exist, but the documentation claims that they're empty. So I have no idea what I'm doing.
- pcwalton 14y agoThe 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.
- dbaupp 14y agoAs a stop gap measure, you can grep the source of the libc module[1], extremely non-optimal though. [1]: https://github.com/mozilla/rust/blob/incoming/src/libcore/libc.rs https://github.com/mozilla/rust/blob/incoming/src/libcore/li...