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
Someone opened an issue on a gem I maintain and I've narrowed it down to what appears to be an inconsistency between JRuby and MRI.
When running my gem's specs in MRI 2.1 (or anything 1.8.7+), this super line just calls inherited as expected. With JRuby 1.7.12, the super line calls whatever method is dynamically defined above, and then calls inherited. I confirmed this by placing puts __method__ right above super. That seems like an issue with JRuby since my understanding of super is that it should only be calling whatever the current method is (inherited), but on the superclass.
It's probably an edge case, but I figured I'd report it since it does seem to be an inconsistency between the two APIs.
The text was updated successfully, but these errors were encountered:
Someone opened an issue on a gem I maintain and I've narrowed it down to what appears to be an inconsistency between JRuby and MRI.
When running my gem's specs in MRI 2.1 (or anything 1.8.7+), this super line just calls
inherited
as expected. With JRuby 1.7.12, the super line calls whatever method is dynamically defined above, and then callsinherited
. I confirmed this by placingputs __method__
right abovesuper
. That seems like an issue with JRuby since my understanding ofsuper
is that it should only be calling whatever the current method is (inherited), but on the superclass.It's probably an edge case, but I figured I'd report it since it does seem to be an inconsistency between the two APIs.
The text was updated successfully, but these errors were encountered: