refactor: assert_suggestion_result() family of functions#3775
Open
hippietrail wants to merge 1 commit into
Open
refactor: assert_suggestion_result() family of functions#3775hippietrail wants to merge 1 commit into
assert_suggestion_result() family of functions#3775hippietrail wants to merge 1 commit into
Conversation
…sion to iteration, including `assert_good_and_bad_suggestions`, which was a holdout still limited to the first few suggestions
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issues
N/A
Description
Some months back I used AI to help me convert the suggestion assertions to find any suggestion rather than just the first three, after failing a couple of attempts to do it with human brain only.
At the time I did not apply the fix also to
assert_good_and_bad_suggestions()because it was a bit more complicated and I wanted to be sure the general fix was fine. It has now long since proven itself.This PR goes a step further by converting these methods from using recursion to iterators, including
assert_good_and_bad_suggestions.I've looked through the code line by line and all tests pass, but because I used more AI than I like in the PR I'd appreciate more eyes checking it. My grasp of all the recursion vs iterator issues in Rust is probably not total at this point too.
There are some tests sprinkled through the code that don't go as far as they should due to the known limitations with the good vs bad assertion. These can be improved over time.
How Has This Been Tested?
cargo testAI Disclosure
Checklist