rust/src/libstd/bool.rs, branch tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try2015-07-20T20:18:06+00:00std: Create separate docs for the primitives2015-07-20T20:18:06+00:00Brian Andersonbanderson@mozilla.com2015-07-20T18:21:02+00:00urn:sha1:8497c428e5da665917304ae404b9b3e7b0a94466
Having the primitive and module docs derived from the same source
causes problems, primarily that they can't contain hyperlinks
cross-referencing each other.
This crates dedicated private modules in `std` to document the
primitive types, then for all primitives that have a corresponding
module, puts hyperlinks in moth the primitive docs and the module docs
cross-linking each other.
This should help clear up confusion when readers find themselves on
the wrong page.
Strip all leading/trailing newlines2015-03-15T16:08:21+00:00Tamir Dubersteintamird@gmail.com2015-03-14T23:29:28+00:00urn:sha1:d51047ded072b412ec18a6f78c1fb80835a477f5grandfathered -> rust12015-01-24T05:48:20+00:00Brian Andersonbanderson@mozilla.com2015-01-24T05:48:20+00:00urn:sha1:b44ee371b8beea77aa1364460acbba14a8516559Add 'feature' and 'since' to stability attributes2015-01-22T00:16:18+00:00Brian Andersonbanderson@mozilla.com2015-01-13T02:40:19+00:00urn:sha1:94ca8a361026d1a622a961e8dc8cacc331ed1ac3std: Remove public bool,tuple,unit modules2014-12-19T03:13:32+00:00Alex Crichtonalex@alexcrichton.com2014-12-19T03:13:32+00:00urn:sha1:1b42e890bf99d37a9e6447912c75c5b5e4695c4e
This commit modifies rustdoc to not require these empty modules to be public in
the standard library. The modules still remain as a location to attach
documentation to, but the modules themselves are now private (don't have to
commit to an API). The documentation for the standard library now shows all of
the primitive types on the main index page.
core: Inherit the bool module2014-05-07T15:14:56+00:00Alex Crichtonalex@alexcrichton.com2014-05-01T04:11:17+00:00urn:sha1:6636215a44b27d1806a2ac646bde1d4ecaa801c4Replace all ~"" with "".to_owned()2014-04-19T00:25:34+00:00Richo Healeyricho@psych0tik.net2014-04-16T01:17:48+00:00urn:sha1:919889a1d688a6bbe2edac8705f048f06b1b455cstd: Change assert_eq!() to use {} instead of {:?}2014-03-01T07:01:54+00:00Alex Crichtonalex@alexcrichton.com2014-02-28T09:23:06+00:00urn:sha1:02882fbd7edcb8d0d152afcdc8571216efcbd664
Formatting via reflection has been a little questionable for some time now, and
it's a little unfortunate that one of the standard macros will silently use
reflection when you weren't expecting it. This adds small bits of code bloat to
libraries, as well as not always being necessary. In light of this information,
this commit switches assert_eq!() to using {} in the error message instead of
{:?}.
In updating existing code, there were a few error cases that I encountered:
* It's impossible to define Show for [T, ..N]. I think DST will alleviate this
because we can define Show for [T].
* A few types here and there just needed a #[deriving(Show)]
* Type parameters needed a Show bound, I often moved this to `assert!(a == b)`
* `Path` doesn't implement `Show`, so assert_eq!() cannot be used on two paths.
I don't think this is much of a regression though because {:?} on paths looks
awful (it's a byte array).
Concretely speaking, this shaved 10K off a 656K binary. Not a lot, but sometime
significant for smaller binaries.
Remove std::bool::{Bool, all_values}2014-02-25T08:52:51+00:00Brendan Zabarauskasbjzaba@yahoo.com.au2014-02-22T19:41:38+00:00urn:sha1:6efa3c63d0be329b466223843bafa2a299f7d485
These were never used outside of the tests
Remove std::from_str::FromStr from the prelude2014-02-25T05:22:26+00:00Brendan Zabarauskasbjzaba@yahoo.com.au2014-02-23T01:29:42+00:00urn:sha1:84a8893f19c4cf87355984c8d5fa604a5828161a