about summary refs log tree commit diff
path: root/src/libcore
AgeCommit message (Collapse)AuthorLines
2019-02-12Auto merge of #58341 - alexreg:cosmetic-2-doc-comments, r=steveklabnikbors-201/+205
Cosmetic improvements to doc comments This has been factored out from https://github.com/rust-lang/rust/pull/58036 to only include changes to documentation comments (throughout the rustc codebase). r? @steveklabnik Once you're happy with this, maybe we could get it through with r=1, so it doesn't constantly get invalidated? (I'm not sure this will be an issue, but just in case...) Anyway, thanks for your advice so far!
2019-02-12Remove some dead code from libcoregnzlbg-14/+0
These macros are not required to glue the `core_arch` crate anymore.
2019-02-12Auto merge of #58098 - oli-obk:maybe_allow_internal_unstable, r=petrochenkovbors-2/+4
Require a list of features in `#[allow_internal_unstable]` The blanket-permission slip is not great and will likely give us trouble some point down the road.
2019-02-12Add doctests for str::escape_*Simon Sapin-3/+93
2019-02-12Make the prema-unstable char::escape_debug_ext method crate-privateSimon Sapin-3/+1
2019-02-12Move str::escape_* to libcoreSimon Sapin-47/+169
2019-02-12Add internal impl_fn_for_zst macro for "named closure types"Simon Sapin-113/+75
2019-02-12Auto merge of #58246 - pmccarter:master, r=oli-obkbors-20/+95
Make `saturating_add` and `saturating_sub` `const` functions Fixes #58030
2019-02-11Require a list of features to allow in `allow_internal_unstable`Oliver Scherer-2/+4
2019-02-10libs: doc commentsAlexander Regueiro-138/+142
2019-02-10tests: doc commentsAlexander Regueiro-60/+60
2019-02-10rustc: doc commentsAlexander Regueiro-4/+4
2019-02-10Auto merge of #58361 - GuillaumeGomez:rollup, r=GuillaumeGomezbors-5/+8
Rollup of 16 pull requests Successful merges: - #57259 (Update reference of rlibc crate to compiler-builtins crate) - #57740 (Use `to_ne_bytes` for converting IPv4Addr to octets) - #57926 (Tiny expansion to docs for `core::convert`.) - #58157 (Add Cargo.lock automatically adding message) - #58203 (rustdoc: display sugared return types for async functions) - #58243 (Add trait alias support in rustdoc) - #58262 (Add #[must_use] message to Fn* traits) - #58295 (std::sys::unix::stdio: explain why we do into_raw) - #58297 (Cleanup JS a bit) - #58317 (Some writing improvement, conciseness of intro) - #58324 (miri: give non-generic functions a stable address) - #58332 (operand-to-place copies should never be overlapping) - #58345 (When there are multiple filenames, print what got interpreted as filenames) - #58346 (rpath computation: explain why we pop()) - #58350 (Fix failing tidy (line endings on Windows)) - #58352 (miri value visitor: use `?` in macro) Failed merges: r? @ghost
2019-02-10Rollup merge of #58262 - taiki-e:must_use, r=estebankGuillaume Gomez-3/+3
Add #[must_use] message to Fn* traits This PR adds `#[must_use]` message to `Fn*` traits. Related: #57549 r? @estebank
2019-02-10Rollup merge of #57926 - icefoxen:test-doc-pr, r=frewsxcvGuillaume Gomez-1/+4
Tiny expansion to docs for `core::convert`. This is not really significant, accept or reject as you wish. I just want to make sure I understand how the PR process works and that I'm doing it right before doing a bigger one for #33417.
2019-02-10Rollup merge of #57259 - king6cong:master, r=alexcrichtonGuillaume Gomez-1/+1
Update reference of rlibc crate to compiler-builtins crate None
2019-02-10Auto merge of #58129 - RalfJung:maybe-uninit, r=cramertjbors-11/+57
MaybeUninit: some docs, rename into_inner -> into_initialized, return &mut from set
2019-02-10it is okay not to use into_innerRalf Jung-0/+1
2019-02-09Fix exhaustion of inclusive range try_fold and try_rfoldMatthieu M-5/+33
2019-02-09Rollup merge of #58275 - RalfJung:miri-test-libcore, r=Mark-SimulacrumMazdak Farrokhzad-0/+38
libcore, liballoc: disable tests in Miri I am going to run the libcore and liballoc unit test suites in Miri. Not all tests pass. This PR disables a whole bunch of tests when running in Miri, to get us to a baseline from which I can investigate failures. Cc @SimonSapin @alexcrichton
2019-02-08Use write_char for writing padding charactersNick Fitzgerald-22/+8
Removes some unsafe *and* saves almost half a kilobyte of code size.
2019-02-08Also de-duplicate 32- and 64-bit number formatting on wasm32Nick Fitzgerald-8/+18
2019-02-07Add unstable feature attribute for unsigned const saturating add/sub ↵Patrick McCarter-0/+2
intrinsics #58030
2019-02-07Refactor const saturating intrinsics emulation and add unstable feature ↵Patrick McCarter-0/+2
attribute #58030
2019-02-07disable tests in MiriRalf Jung-0/+38
2019-02-07also fix bad use of shared ref in split_at_mutRalf Jung-1/+1
2019-02-07Un-monomorphize and inline formatting with paddingNick Fitzgerald-29/+57
The generic `F` in `with_padding` was causing a bunch of stuff to get inlined that otherwise needn't be, blowing up code size.
2019-02-07Rollup merge of #58185 - GuillaumeGomez:images-url, r=SimonSapinGuillaume Gomez-3/+1
Remove images' url to make it work even without internet connection Needed for local std docs mainly. cc @SimonSapin r? @QuietMisdreavus
2019-02-07Rollup merge of #57848 - jrvanwhy:transmute-export-doc, r=QuietMisdreavusGuillaume Gomez-0/+1
Generate a documentation page for core::mem::transmute. In `#[no_std]` environments, `std::mem::transmute` is unavailable. Searching for "core transmute" online only pulls up `core::intrinsics::transmute`, which is behind the (unstable) `core_intrinsics` feature flag. Users wishing to use transmute in `#[no_std]` environments typically should use `core::mem::transmute` instead, as it is stable. This documentation makes `core::mem::transmute` discoverable.
2019-02-07De-duplicate write_prefix lambda in pad_integralNick Fitzgerald-11/+20
For smaller code size.
2019-02-07De-duplicate number formatting implementations for smaller code sizeNick Fitzgerald-31/+38
Instead of inlining the same logic into every number formatting implementation, pull it out into a function that each of the number formatting impls call into.
2019-02-07Add #[must_use] message to Fn* traitsTaiki Endo-3/+3
2019-02-07Remove images' url to make it work even without internet connectionGuillaume Gomez-3/+1
2019-02-06Change RawWaker constructor to const fnMatthias Einwag-4/+24
2019-02-06Allow const assignment for int saturating_sub() for #58030Patrick McCarter-10/+44
2019-02-06Fix broken grammar in iter::from_fn() docsSebastian Dröge-4/+2
2019-02-06add tracking issueRalf Jung-1/+1
2019-02-06remove now-unneeded raw ptr castsRalf Jung-3/+3
2019-02-06fix doctestsRalf Jung-1/+2
2019-02-05Allow const assignment for int saturating_add() calls for #58030Patrick McCarter-10/+47
2019-02-05fix str mutating through a ptr derived from &selfRalf Jung-3/+19
2019-02-05fix doctestRalf Jung-2/+2
2019-02-06Rollup merge of #58172 - garyemerson:patch-1, r=steveklabnikkennytm-14/+14
update split docs Some confusion about split popped up at https://news.ycombinator.com/item?id=19080931 since the docs sorta sound like `&str`, `char` and closures are the only types that can be patterns. cc @steveklabnik
2019-02-06Rollup merge of #58145 - taiki-e:poll, r=cramertjkennytm-0/+1
Add #[must_use] to core::task::Poll cc rust-lang/rfcs#2592 r? @withoutboats
2019-02-05review suggestionsMatthias Einwag-2/+9
2019-02-05Apply more review suggestionsMatthias Einwag-3/+11
2019-02-04update split docsgaryemerson-14/+14
Some confusion about split popped up at https://news.ycombinator.com/item?id=19080931 since the docs sorta sound like `&str`, `char` and closures are the only types that can be patterns. cc @steveklabnik
2019-02-04Add #[must_use] to core::task::PollTaiki Endo-0/+1
2019-02-04Remove weasel word in docs for iter's take_while()lukaslueg-2/+1
The phrase "... or some similar thing." is very vague and contributes nothing to understanding the example. Simply removed.
2019-02-04typosRalf Jung-2/+2
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-25 07:50:04 +0000