summary refs log tree commit diff
path: root/src/doc/reference.md
AgeCommit message (Collapse)AuthorLines
2015-06-18Rollup merge of #26349 - petrochenkov:bitwise, r=steveklabnikManish Goregaokar-5/+7
I'm surprised that bitwise operators `&`, `|` and `^` are implemented for `bool` arguments, because inspection of boolean's bits is not something that should be encouraged and because `&&` -> `&` is a common typo, but if they are implemented, then their behavior should be documented.
2015-06-18Rollup merge of #26342 - steveklabnik:quix_reference_fix, r=alexcrichtonManish Goregaokar-3/+14
https://github.com/rust-lang/rust/pull/26323/files#r32503568
2015-06-17Document behavior of bitwise operators with boolean argumentsVadim Petrochenkov-5/+7
2015-06-16Auto merge of #24738 - joliv:patch-2, r=steveklabnikbors-2/+5
The "unit value" is a value of the "unit type," not the "unit value type." Regardless of correctness, this straight syntax is easier to grok. Part of #16676 Sorry if something's off here, it's my first pull request to rust!
2015-06-16One more consistency fix in the referenceSteve Klabnik-3/+14
https://github.com/rust-lang/rust/pull/26323/files#r32503568
2015-06-15Add unit type info and update associated linkjoliv-2/+5
Fixes #25244
2015-06-15Significantly simplify generic exampleSteve Klabnik-10/+9
Fixes #26320
2015-06-12[reference] Fix typo in extern fn sectionMatt Brubeck-1/+1
2015-06-10Add explanation for E0116 and update the error message.Nick Hamann-1/+1
Also updates the reference on this point.
2015-06-09Rollup merge of #26111 - tshepang:consistency, r=brsonSteve Klabnik-1/+0
2015-06-09Rollup merge of #26113 - tshepang:avoid-abbreviations, r=steveklabnikManish Goregaokar-6/+6
2015-06-09Rollup merge of #26112 - tshepang:readability, r=steveklabnikManish Goregaokar-3/+7
2015-06-09reference: that looks better without those abbreviationsTshepang Lekhonkhobe-6/+6
2015-06-09reference: improve readabilityTshepang Lekhonkhobe-3/+7
2015-06-09reference: get consistent by removing unneeded whitespaceTshepang Lekhonkhobe-1/+0
2015-06-07Make all leaks safe in language referencediwic-1/+1
Since it was determined that no leaks were unsafe, some of the documentation is still not clear about this. Here's one example.
2015-06-04Fix doctest (fixup –#25900)Manish Goregaokar-16/+17
2015-06-04Rollup merge of #25900 - lorenzb:more_about_types, r=nikomatsakisManish Goregaokar-0/+140
My main sources of information are [RFC401](https://github.com/rust-lang/rfcs/blob/master/text/0401-coercions.md), the rust IRC channel, and a bunch of experiments to figure out what `rustc` currently supports. Note that the RFC calls for some coercion behaviour that is not implemented yet (see #18469). The documentation in this PR mostly covers current behaviour of rust and doesn't document the future behaviour. I haven't written about receiver expression coercion. I would be happy to rewrite/adapt the PR according to feedback. r? @steveklabnik
2015-06-03Remove #[static_assert]Steve Klabnik-9/+0
This was always a weird feature, and isn't being used in the compiler. Static assertions should be done better than this. This implements RFC #1096. Fixes #13951 Fixes #23008 Fixes #6676 This is behind a feature gate, but that's still a [breaking-change]
2015-05-30Extend rust reference with a section about type coercionsLorenz-0/+120
2015-05-30Extend rust reference with a section about subtypingLorenz-0/+20
2015-05-28floating-point types are machine types, not machine-dependent typesLiigo Zhuang-2/+2
2015-05-21Document the debug_assertions cfg optionMatt Brubeck-0/+4
2015-05-15Update reference.mdMichael Rosenberg-0/+8
Added `Deref` to the "Special Traits" section
2015-05-13Fix link to RFC 255 in Reference.Nick Hamann-1/+3
2015-05-13Fix test failure in the referenceSteve Klabnik-0/+5
2015-05-12Improve wording for the "Trait objects" section of the reference.Nick Hamann-7/+15
2015-05-12Expand the "Traits" section of the reference.Nick Hamann-0/+40
2015-05-12Correct various small points, expand some sections, while avoidingNiko Matsakis-52/+151
too much detail.
2015-05-11Rollup merge of #25283 - steveklabnik:gh24999, r=alexcrichtonSteve Klabnik-20/+17
and remove references to the unit type, which no longer exists Fixes #24999
2015-05-11Rollup merge of #25282 - badboy:reference-macro-1, r=alexcrichtonSteve Klabnik-1/+1
As mentioned in https://github.com/rust-lang/rust/issues/16676#issuecomment-100676326 this makes it a little bit more correct. I'm a bit unsure whether or not it should be explained that the transcriber can be wrapped in parentheses or curly braces if necessary.
2015-05-11Fix links in the refereceSteve Klabnik-20/+17
and remove references to the unit type, which no longer exists Fixes #24999
2015-05-11Rollup merge of #25291 - johannhof:let-expressions-example, r=steveklabnikManish Goregaokar-0/+14
Maybe it's me, but I really needed an example to understand if let and refutable statements. Playpen: http://is.gd/mjX3Gf Let me know if the variable names are too, uh, culinary.
2015-05-11Rollup merge of #25290 - bluss:docfixes, r=steveklabnikManish Goregaokar-13/+14
Several Minor API / Reference Documentation Fixes - Fix a few small errors in the reference. - Fix paper cuts in the API docs. Fixes #24882 Fixes #25233 Fixes #25250
2015-05-11docs: Fixes in Reference Chapter 6.1Ulrik Sverdrup-13/+14
2015-05-11Four spaces indent, rephrasingJohann-4/+7
2015-05-11Add if let expressions exampleJohann Hofmann-0/+11
2015-05-11Docs: Compile-time bounds check in index expressionJohann Hofmann-4/+11
The reference was claiming all vectors all bounds-checked at run-time, when constant vectors are usually checked at compile-time. For the changed example see http://is.gd/28ak9E
2015-05-10Remove extra parenthesesJan-Erik Rediger-1/+1
2015-05-09Convert #[lang=".."] to #[lang = ".."] for docs too.Nick Hamann-1/+1
2015-05-09Rollup merge of #25216 - barosl:no-more-task, r=ManishearthManish Goregaokar-1/+1
I've found that there are still huge amounts of occurrences of `task`s in the documentation. This PR tries to eliminate all of them in favor of `thread`.
2015-05-08Remove references to deprecated `extern crate "foo" as bar` syntaxCarol Nichols-5/+4
This syntax was removed in b24a3b8 but references remained in the grammar, the reference, rustdoc generation, and some auxiliary test files that don't seem to have been used since 812637e.
2015-05-09Squeeze the last bits of `task`s in documentation in favor of `thread`Barosl Lee-1/+1
An automated script was run against the `.rs` and `.md` files, subsituting every occurrence of `task` with `thread`. In the `.rs` files, only the texts in the comment blocks were affected.
2015-05-07Rollup merge of #25052 - jooert:misc_attr_reference, r=steveklabnikSteve Klabnik-5/+4
Unsafe destructors were removed, added remarks about needed feature gates. cc #16676 r? @steveklabnik
2015-05-03Clean up the grammar around the inline attributeJake Goulding-6/+6
2015-05-02Update "Miscellaneous attributes" section of reference manualJohannes Oertel-5/+4
2015-05-01Rollup merge of #24992 - steveklabnik:gh24730, r=alexcrichtonManish Goregaokar-1/+8
Fixes #24730 r? @alexcrichton
2015-05-01Rollup merge of #24981 - carols10cents:remove-more-priv, r=alexcrichtonManish Goregaokar-2/+1
Hi! While researching stuff for the reference and the grammar, I came across a few mentions of using the `priv` keyword that was removed in 0.11.0 (#13547, #8122, rust-lang/rfcs#26, [RFC 0026](https://github.com/rust-lang/rfcs/blob/master/text/0026-remove-priv.md)). One occurrence is a mention in the reference, a few are in comments, and a few are marking test functions. I left the test that makes sure you can't name an ident `priv` since it's still a reserved keyword. I did a little grepping around for `priv `, priv in backticks, `Private` etc and I think the remaining instances are fine, but if anyone knows anywhere in particular I should check for any other lingering mentions of `priv`, please let me know and I would be happy to! :fallen_leaf: :ocean:
2015-04-30Describe (a,) vs (a) in docsSteve Klabnik-1/+8
Fixes #24730
2015-04-30Auto merge of #24924 - carols10cents:grammar-improvements, r=pnkfelixbors-5/+0
I'm interested in helping out with #16676 but more in the grammar than the reference-- here's my first chunk, more to come!! :tada: I did pull a bit *out* of the reference, though, that was more relevant to the grammar but wasn't moved over as part of #24729. I'm looking at, e.g. https://github.com/rust-lang/rust/blob/master/src/libsyntax/ast.rs, as the source of truth, please let me know if I should be checking against something else instead/in addition. r? @steveklabnik