Fixed bug that was comparing string to listNodes #561
Merged
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
MicahGale
added
the
bugs
MicahGale
changed the title
MicahGale
force-pushed
the
552-listnode-comparison-is-blocking-contains-for-listnode
branch
from
874af41
to
a129b17
Compare
tjlaboss
approved these changes
Oct 7, 2024
MicahGale
deleted the
552-listnode-comparison-is-blocking-contains-for-listnode
branch
Merged
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.
Description
This bug is caused by a shortcut being in a fill. This is because it tries
"(" in list_node.nodes'. Due to the shortcut there is aListNode(shortcut) in this list which requires aeq` test.This was fixed by
Fixes #552
Checklist