about summary refs log tree commit diff
path: root/src/doc/reference.md
AgeCommit message (Collapse)AuthorLines
2015-07-05reference: remove stray commaTshepang Lekhonkhobe-1/+1
2015-07-05reference: improve coercions sectionTshepang Lekhonkhobe-41/+66
2015-07-05Rollup merge of #26795 - tshepang:typo, r=steveklabnikSteve Klabnik-1/+1
2015-07-05reference: fix typoTshepang Lekhonkhobe-1/+1
2015-07-05Rollup merge of #26792 - tshepang:follow-idiom, r=steveklabnikSteve Klabnik-4/+2
2015-07-05reference: improve lambda exampleTshepang Lekhonkhobe-4/+2
2015-07-05Rollup merge of #26791 - tshepang:misc-ref-fixes, r=steveklabnikSteve Klabnik-2/+2
One is for grammar, and the other is for clarity
2015-07-05reference: tiny fixesTshepang Lekhonkhobe-2/+2
One is for grammar, and the other is for clarity
2015-07-05Rollup merge of #26788 - tshepang:not-exclamation-marks, r=steveklabnikSteve Klabnik-2/+2
The sentences are also so short that they don't need periods at the end
2015-07-05Rollup merge of #26787 - tshepang:tuple-usage, r=steveklabnikSteve Klabnik-3/+6
2015-07-05Rollup merge of #26785 - tshepang:inference, r=steveklabnikSteve Klabnik-12/+21
…at and integer types
2015-07-05reference: improve examples of the different array typesTshepang Lekhonkhobe-4/+9
2015-07-05reference: that looks like exclamations marks for some fontsTshepang Lekhonkhobe-2/+2
The sentences are also so short that they don't need periods at the end
2015-07-05reference: make tuple usage examples more meaningfulTshepang Lekhonkhobe-3/+6
2015-07-05reference: improve readability of type inference explanations for float and ↵Tshepang Lekhonkhobe-12/+21
integer types
2015-07-01Add netbsd amd64 supportAlex Newman-1/+1
2015-06-26accessing private fields is not safe, and io isn't scaryAlexis Beingessner-3/+0
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.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-24 20:14:42 +0000