-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
UnboundMethod#parameters for an assignment method wrongly returns blank array #2816
Comments
I don't have much to add to this, but wanted to note that it's still a problem in 1.7.19. |
It also looks like it's not a problem with manually defined
So apparently it's only a problem with |
I fixed thereported problem but I noticed this uncovered a class of potential methods where we are not properly reporting back parameter data. I opened up #2817 to track that. Tests should follow with that issue as well. |
Thanks for the prompt fix, @enebo! |
Excellent news, thanks @enebo |
See jruby/jruby#2816 and rspec/rspec-mocks#919 for a discussion of the bug. This is affecting us now that I’m trying to enable partial double verification for rspec-core (rspec/rspec-core#2032) so I thought it worth addressing.
See jruby/jruby#2816 and rspec/rspec-mocks#919 for a discussion of the bug. This is affecting us now that I’m trying to enable partial double verification for rspec-core (rspec/rspec-core#2032) so I thought it worth addressing.
See jruby/jruby#2816 and rspec/rspec-mocks#919 for a discussion of the bug. This is affecting us now that I’m trying to enable partial double verification for rspec-core (rspec/rspec-core#2032) so I thought it worth addressing.
See jruby/jruby#2816 and rspec/rspec-mocks#919 for a discussion of the bug. This is affecting us now that I’m trying to enable partial double verification for rspec-core (rspec/rspec-core#2032) so I thought it worth addressing.
rspec-mocks relies upon
parameters
for verifying doubles to ensure the method signature of the real object supports the provided arguments, and it's not working properly for assignment methods on JRuby due to this bug (see rspec/rspec-mocks#919).The text was updated successfully, but these errors were encountered: