6cabe2b902
1. In the first case, the previous code was failing during type inference due to mismatched structure. Fix is to use the X structure at both points in the code. 2. In the second case, a naive transcription that subsitutes *nothing* in for the omitted statements signified by "..." will actually compile without an error. Furthermore, any pure code could also be substituted for the ellipsis and the code would compile (as the text already states). So to make the example more illustrative, it would be better to include an impure callback, which makes the potential for aliasing immediately obvious to the reader. |
||
|---|---|---|
| .. | ||
| 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