-
Notifications
You must be signed in to change notification settings - Fork 143
Avoid calling >= on unknown receivers in ls command
#1193
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
To solve the problem, the change looks good. However,
ls fools Foodoesn't work when some other methods are missing:Unlike Object instances that we need to consider BasicObject, I think we can assume Classes doesn't undef/change most of these methods:
constants,class_variables,to_s,ancestors,public_instance_methods.But for
<, I guess it might be removed and need to changeif klass < Objecttoif Object > klassin the situation you are assuming.Can you share what kind of situation
:<=is removed? Will:>be removed too?Do you know an existing gem that creates a class without
:<=?The correct fix depends on the situation what you are assuming, and needs to be commented in test code.
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, sorry, I should have added more details! The situation came up in Rubydex where an
undefined method '>='NoMethodError occurred onc >= Classdue to a shadowedsingleton_classreturning an instance rather than the real class (better details in this issue). I believe thesingleton_classis okay due to #1177 and is being fixed in Rubydex, but this raised the idea that flipping the comparison might prevent situations where a foreign object behaved oddly when comparedI've updated my commit with this change:)
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.
Thank you for providing the background 👍
I've confirmed the bug that described in Shopify/rubydex#685 with IRB 1.17.0
So the error is caused by:
However, flipping the operator doesn't solve the problem. It still raises error because the receiver was not a Class that doesn't have
:>=, but was a normal Object.