OpenE2K
/
rust
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

auto merge of #5782 : zofrex/rust/doc-1-tuples, r=thestinger 

As per [the 0.6 release notes](https://github.com/mozilla/rust/wiki/Doc-detailed-release-notes#06-april-2013) single-element tuples are legal. I spotted a couple of places in the documentation that said otherwise, and propose these changes to them.
This commit is contained in:
bors 2013-04-08 16:22:03 -07:00
parent 1968130885 ac9e694d59
commit 786ae0114b
2 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/rust.md
View File

@ -1653,11 +1653,12 @@ Path expressions are [lvalues](#lvalues-rvalues-and-temporaries).
### Tuple expressions
Tuples are written by enclosing two or more comma-separated
Tuples are written by enclosing one or more comma-separated
expressions in parentheses. They are used to create [tuple-typed](#tuple-types)
values.
~~~~~~~~ {.tuple}
(0,);
(0f, 4.5f);
("a", 4u, true);
~~~~~~~~
@ -2578,7 +2579,7 @@ to the record type-constructor. The differences are as follows:
Tuple types and values are denoted by listing the types or values of their
elements, respectively, in a parenthesized, comma-separated
list. Single-element tuples are not legal; all tuples have two or more values.
list.
The members of a tuple are laid out in memory contiguously, like a record, in
order specified by the tuple type.

2
doc/tutorial.md
View File

@ -747,7 +747,7 @@ fn area(sh: Shape) -> float {
Tuples in Rust behave exactly like structs, except that their fields
do not have names. Thus, you cannot access their fields with dot notation.
Tuples can have any arity except for 0 or 1 (though you may consider
Tuples can have any arity except for 0 (though you may consider
unit, `()`, as the empty tuple if you like).
~~~~