MattX opened PR #2400 from improve-finalize-msg
to main
:
Hello! I'm suggesting this quick change that's helped me with debugging. Required information below.
- This change has not been discussed in an issue, but it's a cosmetic change which I don't think warrants deep debate.
- This change adds an offending block identifier to error messages when a
FunctionBuilder
is finalized, but some blocks are not sealed or not filled. This should help with debugging. This also removes confusing / outdated references to dropping theFunctionBuilder
in the messages.- There are no new test cases, because the only change is in an error message. All existing test cases still pass.
- I will assign a random recommended reviewer, but feel free to unassign / reassign the PR.
MattX updated PR #2400 from improve-finalize-msg
to main
:
Hello! I'm suggesting this quick change that's helped me with debugging. Required information below.
- This change has not been discussed in an issue, but it's a cosmetic change which I don't think warrants deep debate.
- This change adds an offending block identifier to error messages when a
FunctionBuilder
is finalized, but some blocks are not sealed or not filled. This should help with debugging. This also removes confusing / outdated references to dropping theFunctionBuilder
in the messages.- There are no new test cases, because the only change is in an error message. All existing test cases still pass.
- I will assign a random recommended reviewer, but feel free to unassign / reassign the PR.
MattX edited PR #2400 from improve-finalize-msg
to main
:
Hello! I'm suggesting this quick change that's helped me with debugging. Required information below.
- This change has not been discussed in an issue, but it's a cosmetic change which I don't think warrants deep debate.
- This change adds an offending block identifier to error messages when a
FunctionBuilder
is finalized, but some blocks are not sealed or not filled. This should help with debugging. This also removes confusing / outdated references to dropping theFunctionBuilder
in the messages.- There are no new test cases, because the only change is in an error message. All existing test cases still pass.
- It doesn't look like I can assign a reviewer, let me know if there's anything I need to do on that front.
fitzgen submitted PR Review.
fitzgen submitted PR Review.
fitzgen submitted PR Review.
fitzgen created PR Review Comment:
We can make this a little less word-y by using
assert!
instead ofif
andpanci!
:assert!( block_data.pristine || self.func_ctx.ssa.is_sealed(block), "FunctionBuilder finalized, but block {} is not sealed", block, ); assert!( block_data.pristine || block_data.filled, "FunctionBuilder finalized, but block {} is not filled", block, );
MattX updated PR #2400 from improve-finalize-msg
to main
:
Hello! I'm suggesting this quick change that's helped me with debugging. Required information below.
- This change has not been discussed in an issue, but it's a cosmetic change which I don't think warrants deep debate.
- This change adds an offending block identifier to error messages when a
FunctionBuilder
is finalized, but some blocks are not sealed or not filled. This should help with debugging. This also removes confusing / outdated references to dropping theFunctionBuilder
in the messages.- There are no new test cases, because the only change is in an error message. All existing test cases still pass.
- It doesn't look like I can assign a reviewer, let me know if there's anything I need to do on that front.
fitzgen submitted PR Review.
fitzgen merged PR #2400.
Last updated: Dec 23 2024 at 13:07 UTC