update docs for std::future::IntoFuture#97876
update docs for std::future::IntoFuture#97876bors merged 1 commit intorust-lang:masterfrom yoshuawuyts:into-future-docs
std::future::IntoFuture#97876Conversation
|
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
|
r? @kennytm (rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
JohnTitor
left a comment
There was a problem hiding this comment.
Thanks for documenting! LGTM
|
I feel like I've seen this work but I cant find any docs or previous examples of a bors approval from multiple ppl sooo, yoolooo lets see if I got this right and have good memory @bors r=JohnTitor,yaahc edit: hmm, is the bors r field literally just a text field that I can shove anything in and it doesn't matter? |
|
📌 Commit a4c4550 has been approved by |
…nTitor,yaahc update docs for `std::future::IntoFuture` Ref rust-lang#67644. This updates the docs for `IntoFuture` providing a bit more guidance on how to use it. Thanks!
…nTitor,yaahc update docs for `std::future::IntoFuture` Ref rust-lang#67644. This updates the docs for `IntoFuture` providing a bit more guidance on how to use it. Thanks!
Rollup of 6 pull requests Successful merges: - rust-lang#97718 (Fix `delayed_good_path_bug` ice for expected diagnostics (RFC 2383)) - rust-lang#97876 (update docs for `std::future::IntoFuture`) - rust-lang#97888 (Don't use __gxx_personality_v0 in panic_unwind on emscripten target) - rust-lang#97922 (Remove redundant calls to reserve in impl Write for VecDeque) - rust-lang#97927 (Do not introduce bindings for types and consts in HRTB.) - rust-lang#97937 (Fix a typo in `test/ui/hrtb/hrtb-just-for-static.rs`) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Ref #67644.
This updates the docs for
IntoFutureproviding a bit more guidance on how to use it. Thanks!