Fix memoization with Hash-like objects as parameters #25
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.
After adding
**kwargs
due to warnings in Ruby 2.7,Hash-like parameters (with
#to_hash
method) convert to Hashwhile passed in dynamically created by Memery method.
For example, instances of
Sequel::Model
.Found Ruby bug: https://bugs.ruby-lang.org/issues/14909
So, changes will be in Ruby 2.8.
And for now we can:
**(;{})
as the additional parameter at method call, what is ugly.eval
and exactly expected arguments,what is dangerous (eval is evil).
First, I've chose the 3th.
But then Jeremy Evans suggest to use
ruby2_keywords
. So, here we're!Additional line of code offensed RuboCop (method length),
so I was forced to refactor method definition.