f9bb7b7768
In struct section of tutorial, make everything more coherent and clear by always using "struct Point". Also, do not prematurely introduce pointers and arrays. Fixes #5240 Signed-off-by: Luca Bruno <lucab@debian.org> |
||
---|---|---|
.. | ||
lib | ||
lib.css | ||
manual.css | ||
prep.js | ||
README | ||
rust.css | ||
rust.md | ||
tutorial-borrowed-ptr.md | ||
tutorial-ffi.md | ||
tutorial-macros.md | ||
tutorial-tasks.md | ||
tutorial.md | ||
version_info.html.template |
The markdown docs are only generated by make when node is installed (use `make doc`). If you don't have node installed you can generate them yourself. Unfortunately there's no real standard for markdown and all the tools work differently. pandoc is one that seems to work well. To generate an html version of a doc do something like: pandoc --from=markdown --to=html --number-sections -o build/doc/rust.html doc/rust.md && git web--browse build/doc/rust.html The syntax for pandoc flavored markdown can be found at: http://johnmacfarlane.net/pandoc/README.html#pandocs-markdown A nice quick reference (for non-pandoc markdown) is at: http://kramdown.rubyforge.org/quickref.html