Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Use actual impl module to test bindability. Fixes #4477. #4521
This fixes #4477 by not using the origin module/class to test bindable hierarchy but instead using the actual implementation module. I'm not sure why it was doing the latter before, but it meant that any methods captured from a module were not bindable to class hierarchies that included that module (since the module was hidden behind a Prepended or IncludedModule origin).
This seems like the proper logic, but I'm doing it as a PR to check CI before pushing forward for 220.127.116.11.
There may be tests for this we don't pass but I could not find them.