- 08 5月, 2015 1 次提交
-
-
由 Alex Crichton 提交于
This commit is an implementation of [RFC 1066][rfc] where the conclusion was that leaking a value is a safe operation in Rust code, so updating the signature of this function follows suit. [rfc]: https://github.com/rust-lang/rfcs/blob/master/text/1066-safe-mem-forget.md Closes #25186
-
- 07 5月, 2015 38 次提交
-
-
由 bors 提交于
The last one (at least for the moment
😃 ). r? @alexcrichton -
由 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 提交于
-
由 Steve Klabnik 提交于
-
由 Steve Klabnik 提交于
I know this is the most trivial thing since it's *just* the model lexer, not the real lexer, but [it is simpler to read](https://github.com/rust-lang/rust/issues/15883#issuecomment-72906431) and it'd be great if it was up to date but [it's been rotting](https://github.com/rust-lang/rust/issues/22379) and this is a tiny bit of that. Thanks!!!!!!
-
由 Steve Klabnik 提交于
-
由 Steve Klabnik 提交于
Unsafe destructors were removed, added remarks about needed feature gates. cc #16676 r? @steveklabnik
-
由 Steve Klabnik 提交于
The error message was misleading, so I adjusted it, and I also added the long diagnostics for this error (resolves one point in #24407). I was unsure about how to phrase the error message. Is “generic parameter binding” the correct term for this?
-
-
由 Andreas Tolfsen 提交于
-
由 bors 提交于
So, I realize this is really late in the game so it's unlikely to be accepted but `FromRawFd`/`FromRawHandle` are necessary for fine grain control over file creation. For example, the current `OpenOptions` does not provide a way to avoid file creation races (there's no way to specify `O_EXCL` or the windows equivalent). Stabilizing these traits and their implementations will give 1.0 users fine-grain control over file creation without committing to any new complex APIs. Additionally, `AsRawFd`/`AsRawHandle` are already stable so I feel that that stabilizing their inverses is a reasonably small change. Disclaimer: I'm asking because my crate, tempfile, depends on this feature.
-
由 bors 提交于
Depends on #24921. r? @alexcrichton
-
由 bors 提交于
cc #19986 r? @Gankro
-
由 bors 提交于
The [UnsafeCell documentation says it is undefined behavior](http://doc.rust-lang.org/nightly/std/cell/struct.UnsafeCell.html), so people shouldn't do it. This happened to catch one case in libstd that was doing this, and I switched that to use an UnsafeCell internally. Closes #13146
-
由 Johannes Oertel 提交于
Closes #20626.
-
由 Johannes Oertel 提交于
Closes #22463.
-
由 Johannes Oertel 提交于
Closes #22258.
-
由 Johannes Oertel 提交于
Closes #22037.
-
由 Johannes Oertel 提交于
Closes #21701.
-
由 Johannes Oertel 提交于
Closes #21562.
-
由 Johannes Oertel 提交于
Closes #21177.
-
由 Michael Wu 提交于
Nothing uses it anymore.
-
由 bors 提交于
Added documentation of the panicking overflow to the `count` and `position` methods of `IteratorExt`, also make them more obvious in the code. Also mention that the `Iterator::next` method of the struct returned by `IteratorExt::enumerate` can panic due to overflow.
-
由 bors 提交于
Previously, `try_write` actually only obtained shared read access (but would return a `RwLockWriteGuard` if that access was successful). Also updates the docs for `try_read` and `try_write`, which were leftover from when those methods returned `Option` instead of `Result`.
-
由 らいどっと 提交于
Remove printing of secret number at final source.
-
由 らいどっと 提交于
This commit depends on #25148.
-
由 Ms2ger 提交于
These constants were added in 6f54ce9a and e8fbd1ce to a consts module that is behind a gate. I have not confirmed that these constants do indeed work on either OSX or iOS. It appears that some of the constants may actually belong in a POSIX module, but I didn't make these changes here because I don't have access to the POSIX standard.
-
由 Steven Allen 提交于
-
- 06 5月, 2015 1 次提交
-
-
由 bors 提交于
Many bounds are currently of the form `T: ?Sized + AsRef<OsStr>` where the argument is `&T`, but the pattern elsewhere (primarily `std::fs`) has been to remove the `?Sized` bound and take `T` instead (allowing usage with both references and owned values). This commit generalizes the possible apis in `std::env` from `&T` to `T` in this fashion. The `split_paths` function remains the same as the return value borrows the input value, so ta borrowed reference is required.
-