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.
Summary
Remove methods that make non-nil objects pretend they are nil.
Details
Removes implementations of
#nil?
that returnedtrue
for classes that are not NilClass; Also updates the#inspect
method forself
in the Aruba console not to return the string"nil"
.Motivation and Context
Having objects respond with
true
to the#nil?
message is super-confusing for humans, machines and cyborgs.How Has This Been Tested?
I ran the specs and cukes.
Types of changes
Checklist: