about summary refs log tree commit diff
path: root/src/libstd
AgeCommit message (Collapse)AuthorLines
2017-05-20Stabilize library features for 1.18.0Steven Fackler-43/+26
Closes #38863 Closes #38980 Closes #38903 Closes #36648
2017-05-20Rollup merge of #42127 - clarcharr:lifetimes, r=Mark-SimulacrumMark Simulacrum-2/+2
Remove unused lifetimes. This was a typo that made it onto master. Noted by @dtolnay in #42127. Also note #41960 which suggests warning these.
2017-05-20Rollup merge of #42091 - maccoda:maccoda/env_docs, r=frewsxcvMark Simulacrum-16/+33
Improving std::env docs Addresses #29351. Hopefully this addresses the following points: > - iterators should use the standard iterator boilerplate like https://doc.rust-lang.org/std/iter/struct.Map.html, this applies to all structs except for JoinPathsError > - JoinPathsError should properly link the function it comes from and use language similar to https://doc.rust-lang.org/std/io/struct.Error.html > - same wording issues with VarError > - functions need to ensure linkage to things they refer to in their descriptions > - Explain the difference between `os` and non-`os` structs and methods
2017-05-20migrate everything to using mem::needs_dropAlexis Beingessner-8/+9
2017-05-20Remove unused lifetimes.Clar Charr-2/+2
2017-05-20Auto merge of #42111 - ollie27:stab, r=Mark-Simulacrumbors-32/+32
Correct some stability versions These were found by running tidy on stable versions of rust and finding features stabilised with the wrong version numbers.
2017-05-20Correct some stability versionsOliver Middleton-32/+32
These were found by running tidy on stable versions of rust and finding features stabilised with the wrong version numbers.
2017-05-20Merge branch 'master' into maccoda/env_docsDylan Maccora-92/+418
2017-05-20Fixed link issue.Dylan Maccora-2/+2
2017-05-19Rollup merge of #42079 - seeekr:patch-1, r=steveklabnikMark Simulacrum-1/+1
fix typo in libstd/sync/mpsc/mod.rs docs
2017-05-19Rollup merge of #42070 - tshepang:env-misc, r=BurntSushiMark Simulacrum-9/+12
misc doc improvements for std::env
2017-05-19Rollup merge of #42056 - sylvestre:master, r=alexcrichtonMark Simulacrum-1/+6
Improve the error management when /proc is not mounted This PR does two things: * Triggers an error on GNU/Linux & Android when /proc/self/exe doesn't exist * Handle the error properly
2017-05-19Rollup merge of #42024 - citizen428:docs/update-exitstatus, r=steveklabnikMark Simulacrum-0/+23
Add documentation for `ExitStatus` As requested in #29370. r? @steveklabnik
2017-05-19Rollup merge of #41870 - excaliburHisSheath:iss29367-windows-docs, r=frewsxcvMark Simulacrum-57/+287
Improve docs in os::windows::ffi and os::windows::fs Part of #29367 This PR makes changes to the documentation in `os::windows::ffi` and `os::windows::fs` with the goal of fleshing them out and bringing them in line with Rust's quality standards. r? @steveklabnik
2017-05-19Fix doc test failure for OpenOptionsExtDavid LeGare-1/+1
2017-05-18Normalize docs in windows::ffi and windows::fsDavid LeGare-57/+64
- Remove `()` parens when referencing functions in docs. - Change some examples to be no_run instead of ignore. - Normalize style in examples for `OpenOptionsExt`. - Fix typo in windows mod docs.
2017-05-18Add documentation for `ExitStatus`Michael Kohl-0/+23
As requested in #29370.
2017-05-18std::env docsDylan Maccora-18/+35
2017-05-18fix typo in libstd/sync/mpsc/mod.rs docsDenis Andrejew-1/+1
2017-05-18misc doc improvements for std::envTshepang Lekhonkhobe-9/+12
2017-05-17Improve the error management when /proc is not mountedSylvestre Ledru-1/+6
This PR does two things: * Triggers an error on GNU/Linux & Android when /proc/self/exe doesn't exist * Handle the error properly
2017-05-16Rollup merge of #41995 - gamazeps:thread-localkey, r=frewsxcvMark Simulacrum-15/+30
[Doc] Add links to the `thread::LocalKey` doc. Part of #29378 . I do not know exactly what should be done for the `cleanup` part, if you have any idea I'll gladly do it. r? @rust-lang/docs
2017-05-16Rollup merge of #41994 - gamazeps:thread-builder, r=GuillaumeGomezMark Simulacrum-11/+38
[Doc] Implrove `thread::Builder`'s doc. Part of #29378 . - Explains *why* we would use the builder instead ofthe free function. - Changes the parent-child explanation for a spawned-caller in `thread::Builder::spawn` - Adds a link to `io::Result` in `thread::Builder` - Corrects the return type doc in `thread::Builder::spawn` r? @rust-lang/docs
2017-05-15Add links to the `thread::LocalKey` doc.Felix Raimundo-15/+30
Part of #29378 .
2017-05-14Improve `thread::Builder` documentation.Felix Raimundo-11/+38
Part of #29378 . - In particular explains *why* we would use the builder instead of the free function. - Changes the parent-child explanation for a spawned-caller. - Add link to `io::Result` in `thread::Builder` - Corrects the `thread::Builder::spawn` documentation.
2017-05-14Add `'static` and `Send` constraints explanations to `thread::spawn`Felix Raimundo-0/+22
Part of #29378.
2017-05-14Explain why `thread::yield_now` could be used.Felix Raimundo-0/+23
Part of #29378.
2017-05-12Rollup merge of #41896 - tshepang:too-long, r=steveklabnikMark Simulacrum-2/+2
doc: break into 2 sentences
2017-05-12Rollup merge of #41860 - mbrubeck:docs, r=nagisaMark Simulacrum-6/+4
Remove wrong or outdated info from CString docs. None
2017-05-11Auto merge of #41684 - jethrogb:feature/ntstatus, r=alexcrichtonbors-3/+38
Windows io::Error: also format NTSTATUS error codes `NTSTATUS` errors may be encoded as `HRESULT`, see [[MS-ERREF]](https://msdn.microsoft.com/en-us/library/cc231198.aspx). These error codes can still be formatted using `FormatMessageW` but require some different parameters to be passed in. I wasn't sure if this needed a test and if so, how to test it. Presumably we wouldn't want to make our tests dependent on localization-dependent strings returned from `FormatMessageW`. Users that get an `err: NTSTATUS` will need to do `io::Error::from_raw_os_error(err|0x1000_0000)` (the equivalent of [`HRESULT_FROM_NT`](https://msdn.microsoft.com/en-us/library/ms693780(VS.85).aspx))
2017-05-11Add testJethro Beekman-0/+14
2017-05-11doc: break into 2 sentencesTshepang Lekhonkhobe-2/+2
2017-05-11Rollup merge of #41192 - zackw:eprintln, r=alexcrichtonCorey Farwell-24/+86
Add `eprint!` and `eprintln!` macros to the prelude. These are exactly the same as `print!` and `println!` except that they write to stderr instead of stdout. Issues #39228 and #40528; previous PR #39229; accepted RFC rust-lang/rfcs#1869; proposed revision to The Book rust-lang/book#615. I have _not_ revised this any since the original submission; I will do that later this week. I wanted to get this PR in place since it's been quite a while since the RFC was merged. Known outstanding review comments: * [x] @steveklabnik requested a new chapter for the unstable version of The Book -- please see if the proposed revisions to the second edition cover it. * [x] @nodakai asked if it were possible to merge the internal methods `_print` and `_eprint` - not completely, since they both refer to different internal globals which we don't want to expose, but I will see if some duplication can be factored out. Please let me know if I missed anything.
2017-05-10Rollup merge of #41854 - gamazeps:thread-spawn-doc, r=steveklabnikSteve Klabnik-6/+56
[Doc] Improve `thread::spawn` documentation Part of #29378 - Add two examples to `thread::spawn` doumentation that show common uses of threads. - Add a link to `thread::Builder` in the `thread::spawn` documentation for configuring threads. - Add a link to `thread::spawn` in `thread::Builder` in order to avoid documentation duplication. r? @steveklabnik
2017-05-10Rollup merge of #41809 - gamazeps:thread-docs, r=steveklabnikSteve Klabnik-61/+91
[DOC] Improve the thread::park and thread::unpark documentation Part of #29378 . Takes care of the documentation for `park`, `park_duration` and also improves the `unpark` example. - `park should` have its module documentation inlined here, and cleaned up. - `park_timeout` could use links to `park`.
2017-05-10Rollup merge of #41531 - steveklabnik:gh40159, r=nagisaSteve Klabnik-1/+35
Add more ways to create a PathBuf to docs The best way to do this wasn't in the documentation, and the ways that were there needed some extra text to elaborate. Fixes #40159 /cc @nagisa
2017-05-10Fix up stability annotations per feedback.Zack Weinberg-7/+7
2017-05-10Revise the eprint(ln)! feature.Zack Weinberg-58/+37
* Factor out the nigh-identical bodies of `_print` and `_eprint` to a helper function `print_to` (I was sorely tempted to call it `_doprnt`). * Update the issue number for the unstable `eprint` feature. * Add entries to the "unstable book" for `eprint` and `eprint_internal`. * Style corrections to the documentation.
2017-05-10Add `eprint!` and `eprintln!` macros to the prelude.Zack Weinberg-0/+83
These are exactly the same as `print!` and `println!` except that they write to stderr instead of stdout. Issue #39228.
2017-05-10Auto merge of #41815 - Yamakaky:improve-backtrace-bottom, r=alexcrichtonbors-8/+47
Improve cleaning of the bottom of the backtrace Following https://github.com/rust-lang/rust/pull/40264. It only cleans the bottom of the trace (after the main). It handles correctly the normal main, tests, benchmarks and threads. I kept `skipped_before` since it will be used later for the cleaning of the top.
2017-05-10Fix typos in docFelix Raimundo-1/+1
2017-05-09Fix tidy errorsDavid LeGare-3/+6
2017-05-09Remove wrong or outdated info from CString docs.Matt Brubeck-6/+4
2017-05-09Don't show the std frames before user code on unwinding.Yamakaky-8/+47
When `RUST_BACKTRACE=1`, remove all frames after `__rust_maybe_catch_panic`. Tested on `main`, threads, tests and benches. Cleaning of the top of the stacktrace is let to a future PR. Fixes #40201 See #41815
2017-05-09Fix warnings in examplesFelix Raimundo-4/+4
2017-05-09Fix linkFelix Raimundo-5/+5
2017-05-09Add more ways to create a PathBuf to docssteveklabnik-1/+35
The best way to do this wasn't in the documentation, and the ways that were there needed some extra text to elaborate. Fixes #40159
2017-05-09Auto merge of #41814 - gamazeps:thread-struct-doc, r=steveklabnikbors-23/+20
[Doc] improve `thread::Thread` and `thread::Builder` documentations Part of #29378 - Adds information about the stack_size when using `Builder`. This might be considered too low level, but I assume that if someone wants to create their own builder instead of using `thread::spawn` they may be interested in that info. - Updates the `thread::Thread` structure doc, mostly by explaining how to get one, the previous example was removed because it was not related to `thread::Thread`, but rather to `thread::Builder::name`. Not much is present there, mostly because this API is not often used (the only method that seems useful is `unpark`, which is documented in #41809).
2017-05-09Address review commentsFelix Raimundo-2/+2
2017-05-09Address review commentsFelix Raimundo-2/+4
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-03 03:21:49 +0000