Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Remove theCoroutineWitness type#144157

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Draft
compiler-errors wants to merge4 commits intorust-lang:master
base:master
Choose a base branch
Loading
fromcompiler-errors:no-witness

Conversation

compiler-errors
Copy link
Member

It's no longer needed, since it just always theCoroutine that it's contained within.

This PR reworks a bit of obligation stalling logic and dtorck constraint behavior, but otherwise it's pretty straightforward.

r?@lcnr or reassign (e.g. to oli, who probably would also be down to review)

@rustbotrustbot added PG-exploit-mitigationsProject group: Exploit mitigations S-waiting-on-authorStatus: This is awaiting some action (such as code changes or more information) from the author. T-clippyRelevant to the Clippy team. T-compilerRelevant to the compiler team, which will review and decide on the PR/issue. T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue. WG-trait-system-refactorThe Rustc Trait System Refactor Initiative (-Znext-solver) labelsJul 18, 2025
@compiler-errors
Copy link
MemberAuthor

@bors2 try@rust-timer queue

(and crater when it's ready)

@rust-timer
Copy link
Collaborator

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

@rust-bors
Copy link

⌛ Trying commita25d83f with merge0282016

To cancel the try build, run the command@bors2 try cancel.

rust-borsbot added a commit that referenced this pull requestJul 18, 2025
Remove the `CoroutineWitness` typeIt's no longer needed, since it just always the `Coroutine` that it's contained within.This PR reworks a bit of obligation stalling logic and dtorck constraint behavior, but otherwise it's pretty straightforward.r? `@lcnr` or reassign (e.g. to oli, who probably would also be down to review)
@rustbotrustbot added the S-waiting-on-perfStatus: Waiting on a perf run to be completed. labelJul 18, 2025
@rust-log-analyzer
Copy link
Collaborator

The jobtidy failed! Check out the build log:(web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)
Checking tidy rustdoc_json...Running eslint on rustdoc JS filesNo error code explanation was removed!tidy: Skipping binary file check, read-only filesystem##[error]tidy error: /checkout/compiler/rustc_ty_utils/src/needs_drop.rs:209: TODO is used for tasks that should be done before merging a PR; If you want to leave a message in the codebase use FIXME##[error]tidy error: /checkout/compiler/rustc_middle/src/ty/print/pretty.rs:908: TODO is used for tasks that should be done before merging a PR; If you want to leave a message in the codebase use FIXMEremoving old virtual environmentcreating virtual environment at '/checkout/obj/build/venv' using 'python3.10' and 'venv'creating virtual environment at '/checkout/obj/build/venv' using 'python3.10' and 'virtualenv'Requirement already satisfied: pip in ./build/venv/lib/python3.10/site-packages (25.1.1)linting python filesAll checks passed!checking python file formatting28 files already formattedchecking C++ file formattingsome tidy checks failedCommand has failed. Rerun with -v to see more details.Build completed unsuccessfully in 0:01:15  local time: Fri Jul 18 20:28:18 UTC 2025  network time: Fri, 18 Jul 2025 20:28:19 GMT##[error]Process completed with exit code 1.Post job cleanup.

@@ -905,6 +905,7 @@ pub trait PrettyPrinter<'tcx>: Printer<'tcx> + fmt::Write {
}
}else{
p!(print_def_path(did, args));
// TODO: Restore witness types?
Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I'll probably leave these out. Otherwise we could have query cycles here.

}else{
// TODO: We could still recurse into upvars and the resume here.
Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This is definitely a FIXME for later. I don't think this has any side effect.

@rust-bors
Copy link

☀️ Try build successful (CI)
Build commit:0282016 (028201683a76a5cd349729c6819c46607119c4e8, parent:8f08b3a32478b8d0507732800ecb548a76e0fd0c)

@rust-timer
Copy link
Collaborator

Queued0282016 with parent8f08b3a, futurecomparison URL.
There are currently 0 preceding artifacts in thequeue.
It will probably take at least ~1.1 hours until the benchmark run finishes.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees

@lcnrlcnr

Labels
PG-exploit-mitigationsProject group: Exploit mitigationsS-waiting-on-authorStatus: This is awaiting some action (such as code changes or more information) from the author.S-waiting-on-perfStatus: Waiting on a perf run to be completed.T-clippyRelevant to the Clippy team.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.WG-trait-system-refactorThe Rustc Trait System Refactor Initiative (-Znext-solver)
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

5 participants
@compiler-errors@rust-timer@rust-log-analyzer@lcnr@rustbot

[8]ページ先頭

©2009-2025 Movatter.jp