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
Safe PrivateMethodTester #2301
base: main
Are you sure you want to change the base?
Safe PrivateMethodTester #2301
Conversation
…, which in previous version just use Any, supported up to 6 arguments in this commit.
*/ | ||
def apply(args: Any*) = new Invocation[T](methodName, args: _*) | ||
def apply() = new Invocation0[T](methodName) | ||
} |
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.
I think we should leave PrivateMethod alone so that no code breaks. We can decide to deprecate it, but that would give folks time to change to PrivateMethodN. Or we could not deprecate it and just let people choose. So please take PrivateMethod and plain old Invocation back to the way it was, then probably add a PrivateMethod0 trait that would use the Invocation0 object.
Safer PrivateMethodTester, with typed arguments vs the existing one that's use only Any.
Related ticket that complained about the problem:
#2300