Is debugging with binding.pry still an issue if runtime checks are disabled? I don't see how sorbet could mitigate this cleanly without digging deeper into one specific Ruby implementation.
BTW: Do the runtime checks work with Rubies other than MRI? Looks like a pure Ruby gem but that's not a guarantee for compatibility.
I haven't tried it, but I'd expect not. Presumably they implement it with TracePoint, which can register and unregister for events (ie I would expect it is implemented without changing the actual structure of the code)
Is debugging with
binding.prystill an issue if runtime checks are disabled? I don't see how sorbet could mitigate this cleanly without digging deeper into one specific Ruby implementation.BTW: Do the runtime checks work with Rubies other than MRI? Looks like a pure Ruby gem but that's not a guarantee for compatibility.
I haven't tried it, but I'd expect not. Presumably they implement it with
TracePoint, which can register and unregister for events (ie I would expect it is implemented without changing the actual structure of the code)As far as I can see, there is no TracePoint usage. They use method_added instead to redefine the method and wrap it with the signature validation.
So, it doesn't seem to have anything MRI specific.