about summary refs log tree commit diff
path: root/src/libcore/future
AgeCommit message (Collapse)AuthorLines
2020-04-25Bump bootstrap compilerMark Rousskov-6/+0
2020-04-05Remove a stack frame from .await callsSteven Fackler-5/+2
2020-03-17Add issue referenceJonas Schievink-1/+1
2020-03-17Clarify commentJonas Schievink-1/+1
2020-03-17Make `ResumeTy` contents privateJonas Schievink-1/+1
2020-03-17Remove useless derives on `GenFuture`Jonas Schievink-1/+0
Not sure why these were there, I guess because this type used to kind of be part of public API?
2020-03-17FormatJonas Schievink-1/+1
2020-03-17Add futures scaffolding to libcoreJonas Schievink-0/+79
2020-02-27Remove spotlight usageGuillaume Gomez-1/+0
2019-12-31Revert "core: add IntoFuture trait and support for await"Wesley Wiser-28/+0
This reverts commit f35517ee861dc012ccc26083dd4520045e2c4f6f.
2019-12-27core: add IntoFuture trait and support for awaitSean McArthur-0/+28
2019-08-08Use associated_type_bounds where applicable - closes #61738Ilija Tovilo-2/+1
2019-08-02Futures: Add link to Waker in trait doc.Bruce Mitchener-1/+3
2019-07-04Switch master to 1.38Mark Rousskov-1/+1
2019-06-27Add suggestion for missing `.await` keywordNathan Corbyn-0/+1
2019-05-27Use .await syntax instead of await!diwic-1/+1
2019-05-13Improve the "must use" lint for `Future`Benjamin Schultzer-1/+1
Co-Authored-By: Mazdak Farrokhzad <twingoow@gmail.com>
2019-04-23Stabilize futures_apiTaylor Cramer-6/+8
2019-04-19core::future::Future: Fix markup typo in docs.Jim Blandy-1/+1
2019-04-19Doc fixes for core::future::Future.Jim Blandy-13/+13
Fixed outdated reference to `waker` argument; now futures are passed a `Context`, from which one can obtain a `waker`. Cleaned up explanation of what happens when you call `poll` on a completed future. It doesn't make sense to say that `poll` implementations can't cause memory unsafety; no safe function is ever allowed to cause memory unsafety, so why mention it here? It seems like the intent is to say that the `Future` trait doesn't say what the consequences of excess polls will be, and they might be bad; but that the usual constraints that Rust imposes on any non-`unsafe` function still apply. It's also oddly specific to say 'memory corruption' instead of just 'undefined behavior'; UB is a bit jargony, so the text should provide examples.
2019-04-18libcore => 2018Taiki Endo-4/+4
2019-04-05Future-proof the Futures APITaylor Cramer-8/+10
2019-02-20Put Future trait into spotlightStjepan Glavina-0/+1
2019-02-20Rollup merge of #58565 - thomaseizinger:typo-future-docs, r=frewsxcvkennytm-1/+1
Fix typo in std::future::Future docs I am not quite sure if this is actually a typo but 1. to me the sentence doesn't make sense if it says "expect" 2. I hope that `Future`s are not really allowed to cause memory unsafety if they are polled after completion.
2019-02-20Rollup merge of #58553 - scottmcm:more-ihle, r=Centrilkennytm-1/+1
Use more impl header lifetime elision Inspired by seeing explicit lifetimes on these two: - https://doc.rust-lang.org/nightly/std/slice/struct.Iter.html#impl-FusedIterator - https://doc.rust-lang.org/nightly/std/primitive.u32.html#impl-Not And a follow-up to https://github.com/rust-lang/rust/pull/54687, that started using IHLE in libcore. Most of the changes in here fall into two big categories: - Removing lifetimes from common traits that can essentially never user a lifetime from an input (particularly `Drop`, `Debug`, and `Clone`) - Forwarding impls that are only possible because the lifetime doesn't matter (like `impl<R: Read + ?Sized> Read for &mut R`) I omitted things that seemed like they could be more controversial, like the handful of iterators that have a `Item: 'static` despite the iterator having a lifetime or the `PartialEq` implementations [where the flipped one cannot elide the lifetime](https://internals.rust-lang.org/t/impl-type-parameter-aliases/9403/2?u=scottmcm). I also removed two lifetimes that turned out to be completely unused; see https://github.com/rust-lang/rust/issues/41960#issuecomment-464557423
2019-02-19Fix typo in std::future::Future docsThomas Eizinger-1/+1
2019-02-17Use more impl header lifetime elisionScott McMurray-1/+1
There are two big categories of changes in here - Removing lifetimes from common traits that can essentially never user a lifetime from an input (particularly `Drop` & `Debug`) - Forwarding impls that are only possible because the lifetime doesn't matter (like `impl<R: Read + ?Sized> Read for &mut R`) I omitted things that seemed like they could be more controversial, like the handful of iterators that have a `Item: 'static` despite the iterator having a lifetime or the `PartialEq` implementations where the flipped one cannot elide the lifetime.
2019-02-12Merging masterMatthias Einwag-1/+1
2019-02-10libs: doc commentsAlexander Regueiro-1/+1
2019-02-05review suggestionsMatthias Einwag-2/+4
2019-02-05Apply more review suggestionsMatthias Einwag-3/+5
2019-02-03Update the future/task APIMatthias Einwag-24/+12
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-13Add #[must_use] message to Iterator and FutureTaiki Endo-1/+1
2018-12-25Remove licensesMark Rousskov-20/+0
2018-12-21Update Pin API to match the one proposed for stabilizationTaylor Cramer-1/+1
Remove pin::Unpin reexport and add Unpin to the prelude. Change Pin associated functions to methods. Rename get_mut_unchecked_ to get_unchecked_mut Remove impl Unpin for Pin Mark Pin repr(transparent)
2018-12-10Add #[must_use] attribute to stdlib traitsFelix Chapman-0/+1
2018-11-10Fix documentation typos.Bruce Mitchener-1/+1
2018-09-19Remove spawning from task::ContextTaylor Cramer-227/+34
2018-09-17Cleanup and fix method resolution issueTaylor Cramer-7/+7
2018-09-01Update to a new pinning API.Without Boats-14/+40
2018-08-23move PinMut into pin module and export through stdNiv Kaminer-2/+2
2018-08-19Fix typos found by codespell.Matthias Krüger-2/+2
2018-07-30Implement Unpin for FutureObj and LocalFutureObjTaylor Cramer-0/+3
2018-07-02Implement `UnsafeFutureObj` for `&mut Future`Josef Reinhard Brandl-1/+15
2018-07-02Remove unnecessary `PhantomData` fieldJosef Reinhard Brandl-4/+2
2018-07-02Add explanation for custom trait objectJosef Reinhard Brandl-1/+18
2018-07-02Fix naming convention issueJosef Reinhard Brandl-1/+1
2018-07-02Improve doc comments for `FutureObj`Josef Reinhard Brandl-3/+4
2018-07-02`UnsafeFutureObj` impl for `PinMut`Josef Reinhard Brandl-3/+3
2018-07-02Add lifetime to `FutureObj`Josef Reinhard Brandl-0/+282
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-23 12:20:53 +0000