summary refs log tree commit diff
path: root/doc/tutorial-borrowed-ptr.md
AgeCommit message (Collapse)AuthorLines
2013-06-21fix text of tutorialsJoris Rehm-3/+3
2013-05-14Replace shared/unique by managed/owned in the tutorialYoungsoo Son-26/+26
2013-03-26librustc: Modify all code to use new lifetime binder syntaxPatrick Walton-10/+10
2013-03-25docs: update to avoid mention of const.Graydon Hoare-5/+4
2013-03-22libcore: Fix obsolete syntax in extfmtPatrick Walton-1/+1
2013-03-18librustc: Make the compiler ignore purity.Patrick Walton-17/+17
For bootstrapping purposes, this commit does not remove all uses of the keyword "pure" -- doing so would cause the compiler to no longer bootstrap due to some syntax extensions ("deriving" in particular). Instead, it makes the compiler ignore "pure". Post-snapshot, we can remove "pure" from the language. There are quite a few (~100) borrow check errors that were essentially all the result of mutable fields or partial borrows of `@mut`. Per discussions with Niko I think we want to allow partial borrows of `@mut` but detect obvious footguns. We should also improve the error message when `@mut` is erroneously reborrowed.
2013-03-02Remove REC, change related tests/docsJihyun Yu-5/+6
2013-02-26doc: Remove references to mut fields. rs=demutingPatrick Walton-157/+4
2013-02-15tests/tutorials: Get rid of `move`.Luqman Aden-1/+1
2013-01-31add if to borrowed ptr tutorialDavid Forsythe-1/+1
2013-01-29Add expected failure annotation on "fixed" example to placate 'make check'.Felix S. Klock II-1/+1
2013-01-29Fixed two examples of erroneous code so their errors match expectation.Felix S. Klock II-2/+4
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.
2012-10-29Fix typo in borrowed pointer tutorial. Closes #3876Brian Anderson-1/+1
2012-10-23Remove binary move from the docsTim Chevalier-1/+1
2012-10-10Copyedit sections 9-11 of the borrowed pointer tutorial (last edits from me)Tim Chevalier-20/+25
2012-10-10Copyedit sections 7 and 8 of the borrowed pointer tutorialTim Chevalier-69/+73
2012-10-10Copyedit sections 5 and 6 of the borrowed pointer tutorialTim Chevalier-71/+77
2012-10-10Copyedit sections 3 and 4 of the borrowed pointer tutorialTim Chevalier-10/+11
2012-10-09Copyedit first two sections of borrowed pointer tutorialTim Chevalier-49/+49
2012-10-02Update to current rules, make (more) examples buildNiko Matsakis-195/+224
2012-09-26tutorial: Remove all references to 'records'. MiscBrian Anderson-10/+13
2012-09-15Make a few more borrowed pointer tutorial examples passBrian Anderson-10/+10
2012-09-15docs: Make supplemental tutorials testableBrian Anderson-21/+85
2012-09-15docs: Add Niko's borrowed pointers tutorialBrian Anderson-0/+702