Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Bind inaccessible methods with informational error output #5823
For #5821 I discovered that we are not properly checking accessibility for methods when setting up their Ruby proxy classes. I have fixed that issue, by providing a JRuby class as the "caller" module, but I believe we need to do a better job helping people open up modules they need for JRuby apps to work.
I propose the following:
I believe the current situation will never scale, since people will see NoMethodError instead of accessibility errors or helpful tips. We have eliminated the JVM's warning but not replaced it with anything of our own. Adding dummy methods would solve this.