about summary refs log tree commit diff
path: root/src/doc/book
AgeCommit message (Collapse)AuthorLines
2016-06-23Switched tense to clarify what is happening in the exampleAlfie John-1/+1
2016-06-19Fixed links in book/compiler-plugins.mdAlexander Stocko-2/+3
2016-06-17Traits where syntax's extra usage example more clearly 吴冉波-2/+2
r? @steveklabnik
2016-06-15Correct use of 'nul' 'null' and capitalizationAlexander Merritt-7/+7
r? @steveklabnik
2016-06-13doc: Fix typoFlorian Berger-1/+1
2016-06-12Auto merge of #34238 - jpreiss:master, r=steveklabnikbors-2/+2
fix typo in primitive-types section on slices
2016-06-11typo fix in loops.mdJames Alan Preiss-1/+1
2016-06-11fix typo in primitive-types section on slicesJames Alan Preiss-1/+1
2016-06-11Auto merge of #34132 - AtheMathmo:no-stdlib, r=steveklabnikbors-4/+20
Note warning of default features on libc The default features of libc include libstd. This should be noted on this page.
2016-06-10Rollup merge of #34129 - jviide:from-string-box-error, r=steveklabnikSeo Sanghyeon-12/+8
Remove a gotcha from book/error-handling.md The book's "Error handling with `Box<Error>`" section talks about `Box<Error>`. In the actual example `Box<Error + Send + Sync>` is used instead so that the corresponding From impls could be used to convert a plain string to an error type. Rust 1.7 added support for conversion from `&str`/`String` to `Box<Error>`, so this gotcha and later references to it can now be removed. r? @steveklabnik
2016-06-08Auto merge of #32202 - arielb1:slice-patterns, r=nikomatsakisbors-3/+3
Implement RFC495 semantics for slice patterns non-MIR translation is still not supported for these and will happily ICE. This is a [breaking-change] for many uses of slice_patterns. [RFC 495 text](https://github.com/rust-lang/rfcs/blob/master/text/0495-array-pattern-changes.md)
2016-06-09fix testsAriel Ben-Yehuda-3/+3
2016-06-07Adding sections and brief explanation of libcJames Lucas-7/+20
Have included an example of a Cargo.toml file containing the libc dependency. The file has been reformatted to use sections. The note on the default features warning is part of the _Using libc_ section but is in bold.
2016-06-07Rollup merge of #34125 - MichaelNecio:book_addition, r=steveklabnikSteve Klabnik-1/+4
Noted that shadowing never destroys a value Fixes issue #33887 r? @steveklabnik
2016-06-07Rollup merge of #34099 - markrcote:functions-copyedit, r=steveklabnikSteve Klabnik-1/+1
Add missing space before parenthesis.
2016-06-07Rollup merge of #34094 - abenga:doc_changes_variable_bindings, r=steveklabnikSteve Klabnik-6/+7
Minor changes to variable bindings chapter * In "*... name as another binding, that's currently in scope, will ...*", *" that's currently in scope"* is not a parenthetical element, and the commas can be omitted. * Other minor changes.
2016-06-07Rollup merge of #34060 - JDemler:master, r=steveklabnikSteve Klabnik-4/+10
Improved documentation for tests/ directory This ambigouity problem was already discussed in the [forums](https://users.rust-lang.org/t/problem-using-external-modules-inside-integration-test-submodule/5312/6).
2016-06-07Minor changes to variable bindings chapterHorace Abenga-6/+7
* In "... name as another binding, that's currently in scope, will ...", ", that's currently in scope, " is not a parenthetical element, and the commas can be omitted. * Other minor changes.
2016-06-06Note warning of default features on libcJames Lucas-0/+3
The default features of libc include libstd. This should be noted on this page.
2016-06-07Remove a gotcha from book/error-handling.mdJoachim Viide-12/+8
The book's "Error handling with Box<Error>" section talks about Box<Error>. In the actual example Box<Error + Send + Sync> is used instead so that the corresponding From impls could be used to convert a plain string to an error type. Rust 1.7 added support for conversion from &str/String to Box<Error>, so this gotcha and later references to it can now be removed.
2016-06-06Noted that shadowing never destroys a valueMichael Necio-1/+4
2016-06-05Add missing space before parenthesis.Mark Côté-1/+1
2016-06-04Book: diagram takes less space and it's more symmetric.Steven Burns-5/+2
2016-06-04Book: fixed syntax coloringSteven Burns-5/+5
2016-06-03Auto merge of #33803 - WiSaGaN:feature/rename-main-thread, r=alexcrichtonbors-11/+11
Rename main thread from "<main>" to "main". Fix issue #33789 We may need to discuss whether this counts as a breaking change since code may check the main thread name against "\<main\>". Discussion is in #33789
2016-06-03document of shared modules for integration testsJakob Demler-2/+7
2016-06-03Fixed ambiguous explanaiton of tests/ directoryJakob Demler-2/+3
2016-06-01Fix a few links in the bookOliver Middleton-9/+10
Links to directories and direct links to doc.rust-lang.org don't work properly when viewing the docs offline so fix them.
2016-05-24Rollup merge of #33810 - tmr232:patch-1, r=ManishearthGuillaume Gomez-1/+1
Fixed link in Rust Book (no-stdlib) Closes #33806
2016-05-24Rollup merge of #33759 - aakloxu:patch-2, r=steveklabnikGuillaume Gomez-2/+0
Fix references links There are duplicate link references in the article and just remove one of them.
2016-05-23Fixed link in Rust Book (no-stdlib)Tamir Bahar-1/+1
Fix a broken link in the rust book.
2016-05-22Rename main thread from "<main>" to "main".Wangshan Lu-11/+11
Fix issue #33789
2016-05-21src/doc: Keep the original style of linksAaklo Xu-2/+2
2016-05-21Rollup merge of #33750 - alx741:fix_typo, r=ManishearthManish Goregaokar-1/+1
book: ownership: fix typo The sentence ends there, so a comma is required. See: http://english.stackexchange.com/questions/1469/when-ending-a-list-with-etc-should-there-be-a-comma-before-etc
2016-05-21Rollup merge of #33747 - postmodern:patch-2, r=ManishearthManish Goregaokar-4/+5
Clarify the English translation of `?Sized` * It wasn't clear whether `?Sized` meant "not `Sized`" or "`Sized` or not `Sized`". According to #rust IRC, it does indeed mean "`Sized` or not `Sized`". * Use the same language as [Trait std::marker::Sized](https://doc.rust-lang.org/std/marker/trait.Sized.html) about how `Sized` is implicitly bound. * Refer to the syntax as `?Sized`, since it's currently the only allowed trait that can follow `?`.
2016-05-21Rollup merge of #33743 - royalstream:royalstream-stack-doc, r=steveklabnikManish Goregaokar-2/+2
Book: small improvement to a table to make it clearer This table is used as an example of four heap values where two of them got deallocated leaving a gap. It also has stack variables. Instead of four stack variables I propose three, that way there's no misleading connection between the number of stack variables and heap variables. But more importantly: three of the four stack variables had the same name (**y**) which could be confusing to a beginner, I changed this as well.
2016-05-20Wording changesPostmodern-3/+3
* Use "special bound syntax" instead of "special syntax". `?Sized` is technically a "bound", but `?Sized` is specialized syntax that _only_ works with `Sized`, and no other Trait. * Replace "constant size" with "sized".
2016-05-20Fix references linksAaklo Xu-4/+2
There are Duplicate link references in the article and the format is incorrect.
2016-05-20Rollup merge of #33745 - postmodern:patch-1, r=steveklabnikGuillaume Gomez-2/+2
Clarify wording in `transmute` example * Change "four eights" to "four u8s" * Change "a 32" to "a u32"
2016-05-19book: ownership: fix typoDaniel Campoverde [alx741]-1/+1
2016-05-19Grammar changePostmodern-3/+4
2016-05-19Keep line-width within 80 columnsPostmodern-2/+3
2016-05-19Clarify the English translation of `?Sized`Postmodern-4/+3
* It wasn't clear whether `?Sized` meant "not `Sized`" or "`Sized` or not `Sized`". According to #rust IRC, it does indeed mean "`Sized` or not `Sized`". * Use the same language as [Trait std::marker::Sized](https://doc.rust-lang.org/std/marker/trait.Sized.html) about how `Sized` is implicitly bound.
2016-05-19Clarify wording in `transmute` examplePostmodern-2/+2
* Change "four eights" to "four u8s" * Change "a 32" to "a u32"
2016-05-19Book: small improvement to a table to make it clearerSteven Burns-2/+2
2016-05-19Rollup merge of #33721 - royalstream:royalstream-doc-highlights, r=ManishearthManish Goregaokar-38/+38
Rust syntax coloring for some ignore, should-panic and no-run snippets. In the book, some code blocks were missing the `rust` specifier which is needed for them to highlight correctly.
2016-05-19Rollup merge of #33720 - mark-summerfield:patch-1, r=steveklabnikManish Goregaokar-0/+2
Clarified that `let(mut x, y) =` only makes x mutable, not y Closes #33716
2016-05-18Rust syntax coloring for some ignore, should-panic and no-run snippets.Steven Burns-38/+38
2016-05-18Clarified that `let(mut x, y) =` only makes x mutable, not ymark-summerfield-0/+2
2016-05-13Updated based on CR feedback.Val Vanderschaegen-3/+3
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-08 02:48:35 +0000