- 09 5月, 2015 7 次提交
-
-
由 Manish Goregaokar 提交于
I deleted one unneccessary 'the' and added the href for [bindings]
-
由 Manish Goregaokar 提交于
… compared
-
由 Manish Goregaokar 提交于
cc #24407
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
Following paragraph says "we've used `*` which..." but code says "rand=\"0.3.0\""
-
由 Manish Goregaokar 提交于
Building with `--target=mipsel-unknown-linux-gnu` currently results in the following errors, fixed by this PR: ``` rustc: x86_64-unknown-linux-gnu/stage2/lib/rustlib/mipsel-unknown-linux-gnu/lib/libstd /vol/rust/src/libstd/os/linux/raw.rs:76:21: 76:28 error: use of undeclared type name `c_ulong` /vol/rust/src/libstd/os/linux/raw.rs:76 pub st_dev: c_ulong, ^~~~~~~ /vol/rust/src/libstd/os/linux/raw.rs:83:22: 83:29 error: use of undeclared type name `c_ulong` /vol/rust/src/libstd/os/linux/raw.rs:83 pub st_rdev: c_ulong, ^~~~~~~ /vol/rust/src/libstd/sys/common/net2.rs:210:52: 210:70 error: unresolved name `libc::TCP_KEEPIDLE` /vol/rust/src/libstd/sys/common/net2.rs:210 setsockopt(&self.inner, libc::IPPROTO_TCP, libc::TCP_KEEPIDLE, ```
-
由 Manish Goregaokar 提交于
If you have 0 references (`&T`) to a resource, presumably, you could have a mutable reference (`&mut T`). So this only start to make sense at having 1 reference to a resource.
-
- 08 5月, 2015 15 次提交
-
-
由 Andrew Straw 提交于
If you have 0 references (`&T`) to a resource, presumably, you could have a mutable reference (`&mut T`). So this only start to make sense at having 1 reference to a resource.
-
由 bors 提交于
* Remove the 2-suffix from some modules * Remove some unused files * Remove double-boxing for `ReentrantMutex`
-
由 Simon Kern 提交于
-
由 Simon Kern 提交于
-
由 bors 提交于
Fix #25076. r? @nikomatsakis
-
由 Simon Kern 提交于
-
由 Simon Kern 提交于
-
由 Tshepang Lekhonkhobe 提交于
-
由 bors 提交于
Ideally this trait implementation would be unstable, requiring crates to opt-in if they would like the functionality, but that's not currently how stability works so the implementation needs to be removed entirely. This may come back at a future date, but for now the conservative option is to remove it. [breaking-change]
-
由 Nick Hamann 提交于
-
由 Nick Hamann 提交于
-
由 bors 提交于
My change in #24797 had a bug, described in that issue’s comments, and first discovered in issue #24918. This fixes it. I tested this new `main.js` by changing the `main.js` content of [a rendered docs page](https://doc.rust-lang.org/std/option/) to this new content. The ‘[−]’ button worked again. I am also including another related fix, because it would require manual merging if I made a separate pull request for it. The page-global ‘[−]’ button currently adds `#` to the end of the URL whenever it is clicked. I am changing its `href` from `#` to `javascript:void(0)` (the same as the `href` for section-specific ‘[−]’ links) to fix that.
-
由 Alex Crichton 提交于
Perform unsafe initialization up front and then only afterward the mutex is in place do we initialize it.
-
由 Alex Crichton 提交于
This module has been removed for quite some time!
-
由 Alex Crichton 提交于
Now that `std::old_io` has been removed for quite some time the naming real estate here has opened up to allow these modules to move back to their proper names.
-
- 07 5月, 2015 18 次提交
-
-
由 bors 提交于
Guard against overflow in `codemap::span_to_lines`. (Revised/expanded version of PR #24976) Make `span_to_lines` to return a `Result`. In `diagnostic`, catch `Err` from `span_to_lines` and print `"(unprintable span)"` instead. ---- There a number of recent issues that report the bug here. See e.g. #24761 and #24954. This change *might* fix them. However, that is *not* its main goal. The main goals are: 1. Make it possible for callers to recover from an error here, and 2. Insert a more conservative check, in that we are also checking that the files match up. ---- As a drive-by, fix #24997 , which was causing my attempts to `make check-stage1` on an `--enable-debug` build to fail.
-
由 Ben Gesoff 提交于
Didn't realise 0.3.0 referred to all 0.3.x versions! Fixed my mistakes. Should have just updated the Cargo.toml now.
-
由 Steve Klabnik 提交于
-
由 Ben Gesoff 提交于
changed paragraphs with discussion of Cargo.lock file to agree with rand version 0.3.0 in the Cargo.tom file.
-
由 bors 提交于
The last one (at least for the moment
😃 ). r? @alexcrichton -
由 Ben Gesoff 提交于
Following paragraph says "we've used `*` which..." but code says "rand=\"0.3.0\""
-
由 Ariel Ben-Yehuda 提交于
-
由 bors 提交于
- Successful merges: #24576, #24966, #25052, #25131, #25137, #25138, #25139, #25141, #25142, #25144, #25146, #25148, #25154, #25156, #25160, #25173 - Failed merges:
-
由 Steve Klabnik 提交于
-
由 Steve Klabnik 提交于
Nothing uses it anymore.
-
由 Steve Klabnik 提交于
Remove printing of secret number at final source.
-
由 Steve Klabnik 提交于
Edit version of #25150. This commit depends on #25148.
-
由 Steve Klabnik 提交于
Let me know if I didn't follow correct procedure - seems a trivial change and no one that can be automatically tested.
-
由 Steve Klabnik 提交于
I noticed this feature added in https://github.com/rust-lang/rust/pull/23289 was missing from the `Search tricks`. Thanks! r? @steveklabnik
-
由 Steve Klabnik 提交于
Enhance Google-ability of `.fold()` by mentioning 'reduce' and 'inject' in the docs. Motivation: [This thread on users.rust-lang.org](https://users.rust-lang.org/t/find-the-shortest-string-in-a-vector/1247)
-
由 Steve Klabnik 提交于
-
-
由 Steve Klabnik 提交于
-