You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using this version of memoist causes the memoization of named arguments to break with a not-very-friendly error message: wrong number of arguments (given 1, expected 0; required keywords: example_argument
Many projects use memoist widely and if they want to use cqm-parsers, this version constraint may inadvertently break other areas of their app where invocations of methods with named arguments occur.
For historical context, named arguments were supported in Ruby starting in 2.0, which was released over 10 years ago. Do you think you could loosen the restriction on the Memoist gem such that it uses a ">=" operator?
Thanks!
The text was updated successfully, but these errors were encountered:
Currently, the Gemspec applies the pessimistic version constraint operator on Memoist:
https://github.com/projecttacoma/cqm-parsers/blob/master/cqm-parsers.gemspec#L31
Using this version of memoist causes the memoization of named arguments to break with a not-very-friendly error message:
wrong number of arguments (given 1, expected 0; required keywords: example_argument
Many projects use memoist widely and if they want to use cqm-parsers, this version constraint may inadvertently break other areas of their app where invocations of methods with named arguments occur.
For historical context, named arguments were supported in Ruby starting in 2.0, which was released over 10 years ago. Do you think you could loosen the restriction on the Memoist gem such that it uses a ">=" operator?
Thanks!
The text was updated successfully, but these errors were encountered: