about summary refs log tree commit diff
path: root/src/libstd/lib.rs
AgeCommit message (Collapse)AuthorLines
2019-07-22Remove uses of mem::uninitialized in std::sys::cloudabiNathan-0/+1
Usages still appear in cloudabi tests and in the reentrant mutex implementation
2019-07-19do not use mem::uninitialized in std::ioRalf Jung-0/+1
2019-07-19warn about deprecated-in-future in most of libstdRalf Jung-1/+1
2019-07-15Update the stdarch submodulegnzlbg-2/+2
2019-07-01Enable mem_take feature in relevant cratesChris Gregory-0/+1
2019-06-22Remove FnBox.Mazdak Farrokhzad-1/+0
2019-06-10std: Remove internal definitions of `cfg_if!` macroAlex Crichton-0/+6
This is duplicated in a few locations throughout the sysroot to work around issues with not exporting a macro in libstd but still wanting it available to sysroot crates to define blocks. Nowadays though we can simply depend on the `cfg-if` crate on crates.io, allowing us to use it from there!
2019-06-03Fix cfg(test) build for x86_64-fortanix-unknown-sgxJethro Beekman-1/+2
2019-05-20stabilize core parts of MaybeUninit and deprecate mem::uninitialized in the ↵Ralf Jung-1/+0
future Also expand the documentation a bit
2019-05-09Fix cfg(test) build on SGXJethro Beekman-0/+1
2019-05-09Stabilize and re-export core::arrayYuki OKUSHI-1/+2
2019-04-26Remove feature gates from std and testsChristopher Serr-1/+0
2019-04-25Rollup merge of #60185 - NieDzejkob:int-error-kind-reexport, r=rkruppeMazdak Farrokhzad-0/+1
Reexport IntErrorKind in std Currently `IntErrorKind` can only be found in `core`. @Centril confirmed on Discord that this is unintentional (should I r? him in this situation?). Should there be a test for this? As far as this *specific* situation goes, I don't think so, I'll risk it and say that there's no way this regresses. However, it might be a good idea to have some tool detect public items in `core` that are not reexported in `std`. Does this belong in tidy, or should that be a separate tool? Is there some rustc-specific *linter*? Unless that's entirely a dumb idea, this should probably get an issue. Note: My local build hasn't finished yet, but it's well past the point where I would expect problems.
2019-04-23Stabilize futures_apiTaylor Cramer-7/+3
2019-04-23Reexport IntErrorKind in stdJakub Kądziołka-0/+1
2019-04-14make lint levels more consistentRalf Jung-3/+4
2019-04-12Stabilize the `alloc` crate.Simon Sapin-1/+0
This implements RFC 2480: * https://github.com/rust-lang/rfcs/pull/2480 * https://github.com/rust-lang/rfcs/blob/master/text/2480-liballoc.md Closes https://github.com/rust-lang/rust/issues/27783
2019-03-31libstd: deny(elided_lifetimes_in_paths)Mazdak Farrokhzad-1/+0
2019-03-18Add todo!() macroAleksey Kladov-1/+2
The use-case of `todo!()` macro is to be a much easier to type alternative to `unimplemented!()` macro.
2019-03-16Rollup merge of #59152 - smmalis37:range_contains, r=SimonSapinkennytm-1/+1
Stabilize Range*::contains. Closes https://github.com/rust-lang/rust/issues/32311. There's also a bit of rustfmt on range.rs thrown in for good measure (I forgot to turn off format-on-save in VSCode).
2019-03-15Auto merge of #58710 - EdorianDark:master, r=sfacklerbors-0/+1
Add clamp for ranges. Implements #44095 Ready for merge
2019-03-12Stabilize Range*::contains.Steven Malis-1/+1
2019-03-09add feature clampDirk Leifeld-0/+1
2019-02-28Use the correct stderr when testing libstdJethro Beekman-1/+1
2019-02-28Fix some imports and pathsTaiki Endo-3/+0
2019-02-28Revert removed #![feature(nll)]Taiki Endo-0/+1
2019-02-28libstd => 2018Taiki Endo-7/+6
2019-02-27Auto merge of #58709 - kornelski:book, r=QuietMisdreavusbors-1/+1
Update book submodule Updates the book to the latest commit This is to include [documentation SEO fix](https://github.com/rust-lang/book/pull/1788) ASAP.
2019-02-26Auto merge of #58357 - sfackler:vectored-io, r=alexcrichtonbors-0/+1
Add vectored read and write support This functionality has lived for a while in the tokio ecosystem, where it can improve performance by minimizing copies. r? @alexcrichton
2019-02-25Auto merge of #58302 - SimonSapin:tryfrom, r=alexcrichtonbors-1/+0
Stabilize TryFrom and TryInto with a convert::Infallible empty enum This is the plan proposed in https://github.com/rust-lang/rust/issues/33417#issuecomment-423073898
2019-02-25Update book submoduleKornel-1/+1
2019-02-22Make std feature list sortedAleksey Kladov-23/+26
This helps to avoid merge conflicts when concurrent PRs append features to the end of the list.
2019-02-17Rollup merge of #58395 - vi:checked_duration_since, r=dtolnaykennytm-0/+1
Instant::checked_duration_since
2019-02-13Add vectored read and write supportSteven Fackler-0/+1
This functionality has lived for a while in the tokio ecosystem, where it can improve performance by minimizing copies.
2019-02-14Rollup merge of #57992 - Matthias247:waker4, r=cramertjMazdak Farrokhzad-2/+0
Update the future/task API This change updates the future and task API as discussed in the stabilization RFC at https://github.com/rust-lang/rfcs/pull/2592. Changes: - Replacing UnsafeWake with RawWaker and RawWakerVtable - Removal of LocalWaker - Removal of Arc-based Wake trait
2019-02-13Stabilize TryFrom and TryIntoSimon Sapin-1/+0
2019-02-13Auto merge of #58235 - jethrogb:jb/sgx-usercall-internals, r=alexcrichtonbors-3/+0
SGX target: simplify usercall internals This moves logic from assembly to Rust and removes the special case for exit/panic handling, merging it with regular usercall handling. Also, this fixes a bug in the exit usercall introduced in a75ae00. The bug would make regular exits look like panics with high probability. It would also with some probability leak information through uncleared registers. cc @VardhanThigle r? @alexcrichton
2019-02-12Merging masterMatthias Einwag-4/+2
2019-02-13Add Instant::checked_duration_since, address #58402.Vitaly _Vi Shukela-0/+1
2019-02-10libs: doc commentsAlexander Regueiro-1/+1
2019-02-07Remove images' url to make it work even without internet connectionGuillaume Gomez-3/+1
2019-02-06SGX target: simplify usercall internalsJethro Beekman-3/+0
This moves logic from assembly to Rust and removes the special case for exit/panic handling, merging it with regular usercall handling. Also, this fixes a bug in the exit usercall introduced in a75ae00. The bug would make regular exits look like panics with high probability. It would also with some probability leak information through uncleared registers.
2019-02-03Update the future/task APIMatthias Einwag-2/+0
This change updates the future and task API as discussed in the stabilization RFC at https://github.com/rust-lang/rfcs/pull/2592. Changes: - Replacing UnsafeWake with RawWaker and RawWakerVtable - Removal of LocalWaker - Removal of Arc-based Wake trait
2019-01-29Update stdsimdgnzlbg-17/+13
2019-01-26Bump bootstrap compiler to 1.33 betaMark Rousskov-3/+0
2019-01-24Rollup merge of #57179 - Xaeroxe:patch-1, r=QuietMisdreavusMazdak Farrokhzad-6/+2
Update std/lib.rs docs to reflect Rust 2018 usage Fixes #56544 This paragraph was written for Rust 2015. Since 2018 has been stable for a while I think we can update it.
2019-01-22Remove unused linksJacob Kiesel-2/+0
2019-01-15Move spin_loop_hint to core::hint moduleClar Fon-0/+1
2019-01-14Stabilize `cfg_target_vendor`, #29718Jethro Beekman-1/+1
2019-01-12Rollup merge of #57441 - ↵Mazdak Farrokhzad-1/+1
VardhanThigle:Vardhan/x86_64-fortanix-unknown-sgx-backtrace-support, r=alexcrichton Supporting backtrace for x86_64-fortanix-unknown-sgx. # Overview Implementing following functions required by `libstd/sys_common` to support `backtrace`: ``` 1. unwind_backtrace 2. trace_fn 3. resolve_symname ``` # Description: The changes here are quite similar to the Cloudabi target `src/libstd/sys/cloudabi/backtrace.rs` The first 2 functions are implemented via calls to libunwind.a that is linked to the `x86_64-fortanix-unknown-sgx` (#56979), we have not implemented functionality needed by `resolve_symname` (or `dladdr`) to reduce SGX TCB. Rather, we print the function address (relative to enclave image base) in `resolve_symname` which can be later translated to correct symbol name (say, via `addr2line`). # Note: For `x86_64-fortanix-unknown-sgx`, the `RUST_BACKTRACE` environment has to be set from within the program running in an enclave. cc: @jethrogb r? @alexcrichton
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-25 01:09:16 +0000