Do not increase depth when evaluating nested goals of NormalizesTo#157718
Do not increase depth when evaluating nested goals of NormalizesTo#157718ShoyuVanilla wants to merge 1 commit into
NormalizesTo#157718Conversation
This comment has been minimized.
This comment has been minimized.
| parent.required_depth = | ||
| parent.required_depth.max(match parent.increase_depth_for_nested { | ||
| IncreaseDepthForNested::Yes => required_depth_for_nested + 1, | ||
| IncreaseDepthForNested::No => required_depth_for_nested, | ||
| }); |
There was a problem hiding this comment.
I've been thinking about about this as this feels brittle. Instead of required_depth, could we change the search graph to track the "min_reached_available_depth" and then required depth is computed as "available_depth - min_reached_available_depth"
that way the way depth is actually tracked doesn't matter anymore
There was a problem hiding this comment.
Sounds good to me. I'll try that way 👍
e59d7fa to
dc07fda
Compare
| &mut self.stack, | ||
| step_kind_from_parent, | ||
| 0, | ||
| None, |
There was a problem hiding this comment.
can you put the min_reachable_for_nested in the UpdateParentGoalCtxt instead?
Hmm, this doesn't help it at all 🤔 |
|
Yeah, we only have |
|
oh 🤔 interesting xd do we have |
|
Yes, they do still exist. But we have very few of them anyway ( |
|
okay, so there are some other goals whose depth we don't properly increase in the old solver but now do in the new one 🤔 what a pain |
|
Indeed. I'll take a look this weekend |
dc07fda to
ee25de1
Compare
This comment has been minimized.
This comment has been minimized.
ee25de1 to
e23e501
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
A job failed! Check out the build log: (web) (plain enhanced) (plain) Click to see the possible cause of the failure (guessed by this bot) |
cc #156619 (comment)
Only the last commit is relevant since this is based on #156619r? lcnr