-
Notifications
You must be signed in to change notification settings - Fork 13.3k
EvaluatedToUnknown
-> EvaluatedToAmbigStackDependent
, EvaluatedToRecur
-> EvaluatedToErrStackDependent
#118685
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 and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…r -> EvaluatedToErrStackDependent
/// implies `EvaluatedToAmbig` implies `EvaluatedToAmbigStackDependent` | ||
/// - `EvaluatedToErr` implies `EvaluatedToErrStackDependent` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't seem to agree with the ordering, unless I am misunderstanding what "implies" means in both the positive and negative case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, it seems wrong.
Though unifying EvaluatedToAmbigStackDependent
and EvaluatedToAmbig
should result in EvaluatedToAmbigStackDependent
🤔 at least when unifying the result of multiple nested goals
I believe the comment to be right and the order here to be wrong 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I thought so too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r=me idk how we should deal with this comment
/// implies `EvaluatedToAmbig` implies `EvaluatedToAmbigStackDependent` | ||
/// - `EvaluatedToErr` implies `EvaluatedToErrStackDependent` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, it seems wrong.
Though unifying EvaluatedToAmbigStackDependent
and EvaluatedToAmbig
should result in EvaluatedToAmbigStackDependent
🤔 at least when unifying the result of multiple nested goals
I believe the comment to be right and the order here to be wrong 🤔
@bors r=lcnr gonna just leave the comment :> |
@bors rollup |
☀️ Test successful - checks-actions |
Finished benchmarking commit (f90f898): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 675.831s -> 675.32s (-0.08%) |
Less confusing names, since the only difference between them and their parallel
EvalutedTo..
is that they are stack dependent.r? lcnr