Add -Ztrait-solver=next-coherence by compiler-errors · Pull Request #112122 · rust-lang/rust (original) (raw)

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 our terms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation12 Commits4 Checks0 Files changed

Conversation

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})

@compiler-errors

Flag that conditionally uses the trait solver only during coherence, for more testing and/or eventual partial-migration onto the trait solver (in the medium- to long-term).

r? @lcnr

@rustbot rustbot added A-testsuite

Area: The testsuite used to check the correctness of rustc

S-waiting-on-review

Status: Awaiting review from the assignee but also interested parties.

T-bootstrap

Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

T-compiler

Relevant to the compiler team, which will review and decide on the PR/issue.

labels

May 31, 2023

@rustbot

Some changes occurred in engine.rs, potentially modifying the public API of ObligationCtxt.

cc @lcnr, @compiler-errors

@compiler-errors

cc @rust-lang/initiative-trait-system-refactor bc of a lack of auto-ping

@BoxyUwU

Why do we need a bool on InferCtxt instead of deriving that information from the flag + whether intercrate mode is set

@compiler-errors

I had originally wanted to make it configurable independently of intercrate mode, but yeah, currently it doesn't need to be a separate bool.

@lcnr

I had originally wanted to make it configurable independently of intercrate mode, but yeah, currently it doesn't need to be a separate bool.

I think that's valuable, would also expect us to e.g. move wf check and mir typeck to the new solver separately from typeck

lcnr

Choose a reason for hiding this comment

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

vibe: can you change use_next_trait_solver to next_trait_solver? idk, use feels somewhat redundant to me and makes stuff harder to read imo

after nits r=me

@lcnr lcnr added S-waiting-on-author

Status: This is awaiting some action (such as code changes or more information) from the author.

and removed S-waiting-on-review

Status: Awaiting review from the assignee but also interested parties.

labels

Jun 6, 2023

@rustbot

Some changes occurred to the core trait solver

cc @rust-lang/initiative-trait-system-refactor

@compiler-errors

@bors

📌 Commit aabdeed has been approved by lcnr

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors

Status: Waiting on bors to run and complete tests. Bors will change the label on completion.

and removed S-waiting-on-author

Status: This is awaiting some action (such as code changes or more information) from the author.

labels

Jun 6, 2023

bors added a commit to rust-lang-ci/rust that referenced this pull request

Jun 7, 2023

@bors

Rollup of 6 pull requests

Successful merges:

r? @ghost @rustbot modify labels: rollup

Labels

A-testsuite

Area: The testsuite used to check the correctness of rustc

S-waiting-on-bors

Status: Waiting on bors to run and complete tests. Bors will change the label on completion.

T-bootstrap

Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

T-compiler

Relevant to the compiler team, which will review and decide on the PR/issue.

WG-trait-system-refactor

The Rustc Trait System Refactor Initiative (-Znext-solver)