about summary refs log tree commit diff
path: root/doc
AgeCommit message (Collapse)AuthorLines
2013-12-11Make 'self lifetime illegal.Erik Price-5/+5
Also remove all instances of 'self within the codebase. This fixes #10889.
2013-12-11Some rustdoc manual fixesCorey Richardson-3/+18
Clarify that it's sundown, and that we don't support magic
2013-12-11proto is gonekud1ing-3/+1
The following files need to be adjusted, too (i can't do it now): - doc/po/ja/rust.md.po - doc/po/rust.md.pot
2013-12-10auto merge of #10880 : cmr/rust/tut++, r=pnkfelixbors-96/+149
Many of them are small. Will squash on request, but I feel like it's easier for everyone (easier to see and back out individual changes) this way.
2013-12-10Remove duplication of libstd docs.Corey Richardson-50/+6
This is literally a copy-paste, there's no need to have this duplication.
2013-12-10Update `Freeze` informationCorey Richardson-1/+4
2013-12-10Tiny fixes to linked list section.Corey Richardson-5/+6
2013-12-10Update Owned to Send, show some types which aren'tCorey Richardson-4/+8
2013-12-10Function declaration takes pats, not exprs.Corey Richardson-1/+1
2013-12-10Clarify newtypeCorey Richardson-1/+1
2013-12-10Clarify arityCorey Richardson-3/+3
2013-12-10Inherited mutabilty clarificationCorey Richardson-3/+2
Also no longer reference mutable fields
2013-12-10loop -> continueCorey Richardson-1/+1
2013-12-10Wildcard changes.Corey Richardson-3/+2
2013-12-10Macro definition is feature gated.Corey Richardson-1/+3
2013-12-10Fix tiny formatting error.Corey Richardson-1/+1
2013-12-10Clarify `as`, mention transmute.Corey Richardson-6/+10
2013-12-10Clarify that strings aren't magical.Corey Richardson-1/+2
2013-12-10Fix tiny formatting error.Corey Richardson-1/+1
2013-12-10Add rustdoc documentation.Corey Richardson-3/+77
2013-12-10auto merge of #10882 : jhasse/rust/patch-1, r=metajackbors-1/+1
typo
2013-12-10Fix grammar error.Corey Richardson-1/+2
2013-12-10Add a link to the wiki's package list and refer to gitCorey Richardson-4/+12
2013-12-10Note that Rust can be embedded.Corey Richardson-1/+1
2013-12-10Fix span.Corey Richardson-1/+1
2013-12-10Explain potentially confusing string example.Corey Richardson-4/+5
Reported be @ElBaha
2013-12-09Add some more commentary to FFI tutorial.Edward Z. Yang-9/+26
Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>
2013-12-09Add missing .comJan Niklas Hasse-1/+1
2013-12-04rewrite part of the tutorialDaniel Micay-46/+361
This begins a rewrite of some sections the tutorial as an introduction to concepts through the implementation of a simple data structure. I think this would be a good way to introduce references, traits and many other concepts too. For example, the section introducing alternatives to ownership can demonstrate a persistent list.
2013-12-02auto merge of #10773 : jvns/rust/patch-1, r=cmrbors-0/+26
The section on closure types was missing, so I added one. I'm new to Rust, so there are probably important things to say about closure types that I'm missing here. I tested the example with the latest Rust nightly.
2013-12-02Add section on closure types to manualJulia Evans-0/+26
2013-12-02Bring the linkage documentation up-to-dateAlex Crichton-19/+223
This includes documentation for all the previous changes done to linking in #10582. Additionally, this brings the list of feature-gates up-to-date with the currently recognized list of features.
2013-11-29Add generation of static libraries to rustcAlex Crichton-8/+4
This commit implements the support necessary for generating both intermediate and result static rust libraries. This is an implementation of my thoughts in https://mail.mozilla.org/pipermail/rust-dev/2013-November/006686.html. When compiling a library, we still retain the "lib" option, although now there are "rlib", "staticlib", and "dylib" as options for crate_type (and these are stackable). The idea of "lib" is to generate the "compiler default" instead of having too choose (although all are interchangeable). For now I have left the "complier default" to be a dynamic library for size reasons. Of the rust libraries, lib{std,extra,rustuv} will bootstrap with an rlib/dylib pair, but lib{rustc,syntax,rustdoc,rustpkg} will only be built as a dynamic object. I chose this for size reasons, but also because you're probably not going to be embedding the rustc compiler anywhere any time soon. Other than the options outlined above, there are a few defaults/preferences that are now opinionated in the compiler: * If both a .dylib and .rlib are found for a rust library, the compiler will prefer the .rlib variant. This is overridable via the -Z prefer-dynamic option * If generating a "lib", the compiler will generate a dynamic library. This is overridable by explicitly saying what flavor you'd like (rlib, staticlib, dylib). * If no options are passed to the command line, and no crate_type is found in the destination crate, then an executable is generated With this change, you can successfully build a rust program with 0 dynamic dependencies on rust libraries. There is still a dynamic dependency on librustrt, but I plan on removing that in a subsequent commit. This change includes no tests just yet. Our current testing infrastructure/harnesses aren't very amenable to doing flavorful things with linking, so I'm planning on adding a new mode of testing which I believe belongs as a separate commit. Closes #552
2013-11-28Register new snapshotsAlex Crichton-9/+9
2013-11-27Be more strict about doc commentsCorey Richardson-5/+7
Previously, `//// foo` and `/*** foo ***/` were accepted as doc comments. This changes that, so that only `/// foo` and `/** foo ***/` are accepted. This confuses many newcomers and it seems weird. Also update the manual for these changes, and modernify the EBNF for comments. Closes #10638
2013-11-26auto merge of #10312 : thestinger/rust/thread_local, r=alexcritchtonbors-0/+2
This provides a building block for fast thread-local storage. It does not change the safety semantics of `static mut`. Closes #10310
2013-11-26add `#[thread_local]` attributeDaniel Micay-0/+2
This provides a building block for fast thread-local storage. It does not change the safety semantics of `static mut`. Closes #10310
2013-11-26librustc: Make `||` lambdas not infer to `proc`sPatrick Walton-2/+2
2013-11-26test: Remove all remaining non-procedure uses of `do`.Patrick Walton-50/+37
2013-11-26librustc: Remove remaining uses of `&fn()` in favor of `||`.Patrick Walton-3/+3
2013-11-26auto merge of #10668 : vky/rust/closure-doc-update, r=alexcrichtonbors-56/+56
2013-11-26Removed unneccessary `_iter` suffixes from various APIsMarvin Löbel-7/+7
2013-11-26Updating docs with updated closure syntax, `&fn` -> `||`Vijay Korapaty-56/+56
2013-11-24auto merge of #10603 : alexcrichton/rust/no-linked-failure, r=brsonbors-113/+3
The reasons for doing this are: * The model on which linked failure is based is inherently complex * The implementation is also very complex, and there are few remaining who fully understand the implementation * There are existing race conditions in the core context switching function of the scheduler, and possibly others. * It's unclear whether this model of linked failure maps well to a 1:1 threading model Linked failure is often a desired aspect of tasks, but we would like to take a much more conservative approach in re-implementing linked failure if at all. Closes #8674 Closes #8318 Closes #8863
2013-11-24Remove linked failure from the runtimeAlex Crichton-113/+3
The reasons for doing this are: * The model on which linked failure is based is inherently complex * The implementation is also very complex, and there are few remaining who fully understand the implementation * There are existing race conditions in the core context switching function of the scheduler, and possibly others. * It's unclear whether this model of linked failure maps well to a 1:1 threading model Linked failure is often a desired aspect of tasks, but we would like to take a much more conservative approach in re-implementing linked failure if at all. Closes #8674 Closes #8318 Closes #8863
2013-11-22minor rewording in the tutorial's `Rc` coverageDaniel Micay-1/+2
2013-11-21auto merge of #10589 : thestinger/rust/doc, r=pcwaltonbors-48/+47
This replaces the old section on managed pointers because the syntax is going to be removed and it's currently feature gated so the examples don't work out-of-the-box. Dynamic mutability coverage can be added after the `Mut<T>` work has landed.
2013-11-21tutorial: alternatives to ownershipDaniel Micay-48/+47
This replaces the old section on managed pointers because the syntax is going to be removed and it's currently feature gated so the examples don't work out-of-the-box. Dynamic mutability coverage can be added after the `Mut<T>` work has landed.
2013-11-21auto merge of #10587 : thestinger/rust/stack, r=pcwaltonbors-7/+5
2013-11-21remove segmented stacks from the manualDaniel Micay-7/+5