你怎么能在Ruby中做一个安全的，向后兼容的“反向monkeypatch”？

If your coworker "opens" ("monkeypatches") a class in Ruby and redefines some important functionality that you need to use, how do you access that original pre-monkeypatched functionality without breaking a system that already relies/has dependencies on his monkeypatched definitions?If your coworker "opens" ("monkeypatches") a cl