summary refs log tree commit diff
path: root/src/libstd/lib.rs
AgeCommit message (Collapse)AuthorLines
2018-11-22update various stdlib docsSteve Klabnik-2/+2
2018-11-22fix more linksSteve Klabnik-5/+5
2018-10-05Stabilize `min_const_fn`Oliver Schneider-1/+1
2018-10-05Auto merge of #54017 - alexcrichton:wasm-atomics2, r=sfacklerbors-0/+1
std: Start implementing wasm32 atomics This commit is an initial start at implementing the standard library for wasm32-unknown-unknown with the experimental `atomics` feature enabled. None of these changes will be visible to users of the wasm32-unknown-unknown target because they all require recompiling the standard library. The hope with this is that we can get this support into the standard library and start iterating on it in-tree to enable experimentation. Currently there's a few components in this PR: * Atomic fences are disabled on wasm as there's no corresponding atomic op and it's not clear yet what the convention should be, but this will change in the future! * Implementations of `Mutex`, `Condvar`, and `RwLock` were all added based on the atomic intrinsics that wasm has. * The `ReentrantMutex` and thread-local-storage implementations panic currently as there's no great way to get a handle on the current thread's "id" yet. Right now the wasm32 target with atomics is unfortunately pretty unusable, requiring a lot of manual things here and there to actually get it operational. This will likely continue to evolve as the story for atomics and wasm unfolds, but we also need more LLVM support for some operations like custom `global` directives for this to work best.
2018-10-02make `CStr::from_bytes_with_nul_unchecked()` a const fnAustin Bonander-0/+1
closes #54678
2018-10-02make `CStr::from_bytes_with_nul_unchecked()` a const fnAustin Bonander-0/+1
closes #54678
2018-09-27Bump to 1.31.0 and bootstrap from 1.30 betaJosh Stone-8/+3
2018-09-24std: Start implementing wasm32 atomicsAlex Crichton-0/+1
This commit is an initial start at implementing the standard library for wasm32-unknown-unknown with the experimental `atomics` feature enabled. None of these changes will be visible to users of the wasm32-unknown-unknown target because they all require recompiling the standard library. The hope with this is that we can get this support into the standard library and start iterating on it in-tree to enable experimentation. Currently there's a few components in this PR: * Atomic fences are disabled on wasm as there's no corresponding atomic op and it's not clear yet what the convention should be, but this will change in the future! * Implementations of `Mutex`, `Condvar`, and `RwLock` were all added based on the atomic intrinsics that wasm has. * The `ReentrantMutex` and thread-local-storage implementations panic currently as there's no great way to get a handle on the current thread's "id" yet. Right now the wasm32 target with atomics is unfortunately pretty unusable, requiring a lot of manual things here and there to actually get it operational. This will likely continue to evolve as the story for atomics and wasm unfolds, but we also need more LLVM support for some operations like custom `global` directives for this to work best.
2018-09-19Auto merge of #53877 - withoutboats:compositional-pin, r=aturonbors-1/+1
Update to a new pinning API. ~~Blocked on #53843 because of method resolution problems with new pin type.~~ @r? @cramertj cc @RalfJung @pythonesque anyone interested in #49150
2018-09-11stabalize infer outlives requirements (RFC 2093).toidiu-1/+0
Co-authored-by: nikomatsakis
2018-09-09stabilize `#[used]`Jorge Aparicio-1/+1
closes #40289
2018-09-07stabilize `#[panic_handler]`Jorge Aparicio-1/+0
2018-09-01Update to a new pinning API.Without Boats-1/+1
2018-08-31Libstd only has `min_const_fn` const fnsOliver Schneider-1/+2
2018-08-27Auto merge of #53227 - nivkner:pin_move, r=RalfJungbors-0/+2
move the Pin API into its own module for centralized documentation This implements the change proposed by @withoutboats in #49150, as suggested by @RalfJung in the review of #53104, along with the documentation that was originally in it, that was deemed more appropriate in module-level documentation. r? @RalfJung
2018-08-27Auto merge of #53441 - toidiu:ak-fix53419, r=nikomatsakisbors-0/+1
fix for late-bound regions Fix for https://github.com/rust-lang/rust/issues/53419 r? @nikomatsakis
2018-08-26Auto merge of #53619 - japaric:panic-handler, r=SimonSapinbors-1/+2
add #[panic_handler]; deprecate #[panic_implementation] r? @SimonSapin cc #44489
2018-08-24check that adding infer-outlives requirement to all crates worksNiko Matsakis-0/+1
2018-08-23Stabilize 'attr_literals' feature.Sergio Benitez-1/+0
2018-08-23add #[panic_handler]; deprecate #[panic_implementation]Jorge Aparicio-1/+2
2018-08-23move pin module to liballoc and reexport thatNiv Kaminer-1/+2
2018-08-23move PinMut into pin module and export through stdNiv Kaminer-0/+1
2018-08-19Stabilize macro_vis_matcherJakub Kozlowski-1/+1
2018-08-17Stabilize `use_extern_macros`Vadim Petrochenkov-1/+1
2018-08-15Make std::io::Error #[non_exhaustive]varkor-0/+1
2018-08-10[nll] libstd: enable feature(nll) for bootstrapmemoryruins-0/+1
2018-08-08Move IPs to assoc constsLinus Färnstrand-0/+1
2018-08-08Make Ipv{4,6}Addr::new const fnsLinus Färnstrand-0/+2
2018-08-05Remove bad features after rebasevarkor-1/+0
2018-08-05Fix stage 2 testsvarkor-1/+1
2018-08-05Remove unnecessary or invalid feature attributesvarkor-17/+1
2018-07-20Update stdsimd to undo an accidental stabilizationAlex Crichton-4/+0
Closes #52403
2018-07-09Implement #[alloc_error_handler]Simon Sapin-1/+2
This to-be-stable attribute is equivalent to `#[lang = "oom"]`. It is required when using the alloc crate without the std crate. It is called by `handle_alloc_error`, which is in turned called by "infallible" allocations APIs such as `Vec::push`.
2018-06-30Bootstrap from 1.28.0-beta.3Mark Simulacrum-4/+1
2018-06-22Review nits and updatesTaylor Cramer-17/+18
Move future_from_generator out of raw Update await to use $crate Renumber errors
2018-06-21async await desugaring and testsTaylor Cramer-2/+2
2018-06-15Add doc for fn keywordGuillaume Gomez-0/+5
2018-06-12Auto merge of #51241 - glandium:globalalloc, r=sfackler,SimonSapinbors-8/+0
Stabilize GlobalAlloc and #[global_allocator] This PR implements the changes discussed in https://github.com/rust-lang/rust/issues/49668#issuecomment-393263510 Fixes #49668 Fixes #27389 This does not change the default global allocator: #36963
2018-06-11Remove some '#[feature]' attributes for stabilized featuresSimon Sapin-1/+0
2018-06-11Remove deprecated heap modulesSimon Sapin-7/+0
The heap.rs file was already unused.
2018-06-11Auto merge of #51442 - tinaun:more-future-impls, r=cramertjbors-0/+1
[futures] add a few blanket impls to std these were defined in the futures crate, but with the core definitions moving to std these would need to move too.
2018-06-11Add #[doc(inline)] in std::taskCrLF0710-0/+2
Add #[doc(inline)] in `std::task` to make the doc seem right.
2018-06-08add a few blanket future impls to stdtinaun-0/+1
2018-06-06Auto merge of #51263 - cramertj:futures-in-core, r=aturonbors-0/+16
Add Future and task system to the standard library This adds preliminary versions of the `std::future` and `std::task` modules in order to unblock development of async/await (https://github.com/rust-lang/rust/issues/50547). These shouldn't be considered as final forms of these libraries-- design questions about the libraries should be left on https://github.com/rust-lang/rfcs/pull/2418. Once that RFC (or a successor) is merged, these APIs will be adjusted as necessary. r? @aturon
2018-06-06Add Future and task system to the standard libraryTaylor Cramer-0/+16
2018-06-04Put doc keyword behind feature flagGuillaume Gomez-0/+1
2018-06-03implement #[panic_implementation]Jorge Aparicio-0/+2
2018-05-17Switch to 1.26 bootstrap compilerMark Simulacrum-8/+1
2018-05-16Stabilize num::NonZeroU*Simon Sapin-1/+0
Tracking issue: https://github.com/rust-lang/rust/issues/49137
2018-05-06Some final touches to ensure `./x.py test --stage 0 src/lib*` workskennytm-2/+2
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-26 22:24:52 +0000