Conversation
Tested with:
# opens doc/index.html
x.py doc --stage 0 --open
x.py doc --stage 0 --open src/doc
# opens doc/book/index.html
x.py doc --stage 0 --open src/doc/book
# opens doc/std/index.html
x.py doc --stage 0 --open src/libstd
# opens doc/proc_macro/index.html
x.py doc --stage 0 --open src/libproc_macro
# opens both
x.py doc --stage 0 --open src/libstd src/libproc_macro
This patch adds `core::future::IntoFuture`. However unlike earlier PRs this patch does not integrate it into the `async/.await` lowering. That integration should be done in a follow-up PR.
Replace sets with lists.
On my machine, an error looks like:
Finished release [optimized] target(s) in 0.29s
Opening doc /git/rust/build/x86_64-unknown-linux-gnu/doc/std/index.html
command 'xdg-open (internal)' did not execute successfully; exit code: 4
command stderr:
gio: file:///git/rust/build/x86_64-unknown-linux-gnu/doc/std/index.html: Error when getting information for file “/git/rust/build/x86_64-unknown-linux-gnu/doc/std/index.html”: No such file or directory
Build completed successfully in 0:00:08
…Gomez Allow using `Self::` in doc Closes rust-lang#70802
…an-DPC Improve E0599 explanation r? @Dylan-DPC
…rk-Simulacrum Add some teams to prioritization exclude_labels r? @Mark-Simulacrum @LeSeulArtichaut
Allow rust-highfive to label issues it creates. This is my first meaningful PR, I am unsure how to test this code so any pointers would be welcome! I am about 50% sure it works.
Add flag to open docs: x.py doc --open This aligns with Cargo's flag `cargo doc --open`. Tested with: ```bash # opens doc/index.html x.py doc --stage 0 --open x.py doc --stage 0 --open src/doc # opens doc/book/index.html x.py doc --stage 0 --open src/doc/book # opens doc/std/index.html x.py doc --stage 0 --open src/libstd # opens doc/proc_macro/index.html x.py doc --stage 0 --open src/libproc_macro # opens both x.py doc --stage 0 --open src/libstd src/libproc_macro ```
…akis Add core::future::IntoFuture This patch reintroduces the `core::future::IntoFuture` trait. However unlike earlier PRs this patch does not integrate it into the `async/.await` lowering since that lead to performance regressions. By introducing the trait separately from the integration, the integration PR can be more narrowly scoped, and people can start trying out the `IntoFuture` trait today. Thanks heaps! cc/ @rust-lang/wg-async-foundations ## References - Original PR adding `IntoFuture` rust-lang#65244 - Open issue to re-land `IntoFuture` (assigned to me) rust-lang#67982 - Tracking issue for `IntoFuture` rust-lang#67644
…an-DPC Clean up E0600 explanation r? @Dylan-DPC
|
@bors r+ rollup=never p=7 |
|
@bors ping |
|
😪 I'm awake I'm awake |
|
@bors r+ rollup=never p=7 |
|
📌 Commit bf1b998 has been approved by |
|
⌛ Testing commit bf1b998 with merge 38ffa6f38ac055ae26dbc80d6cc8a91f6fedb76f... |
|
💔 Test failed - checks-azure |
|
spurious @bors retry |
|
💔 Test failed - checks-azure |
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
|
@bors treeclosed=1000 GitHub outage. |
|
@bors untreeclosed Github outage has ended: https://www.githubstatus.com/incidents/6tcfpztf6j9m |
|
@bors treeclosed- |
|
@bors retry |
|
☀️ Test successful - checks-azure |
Successful merges:
Self::in doc #71289 (Allow usingSelf::in doc)Failed merges:
r? @ghost