FIX: Don't loop forever if an RR CLASS doesn't match the apex CLASS. #457
Conversation
This file contains 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
partim
reviewed
Dec 18, 2024
| continue; | ||
| } | ||
| if apex == first || first.owner().ends_with(apex.owner()) { | ||
| for rr in self.slice { |
There was a problem hiding this comment.
For-looping on a thing that you are also currently modifying sounds scary and unintuitive. I’m kind of surprised the compiler lets you do this.
There was a problem hiding this comment.
In my opinion, signing needs to be changed to not allow multiple classes. There is no need to that feature and it just make the code more complex.
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.
Fixes #456 in my local testing.