[BUG] - binding.pry

[scottbarrow]

Describe the bug
Expected binding.pry to work as it does with pry, pry-rails, pry-debugger since pry is a dependency of this gem.
It would be great if Jard was backwards compatible so that users who prefer binding.pry can use it alongside other team members wishing to use Jard

To Reproduce
Steps to reproduce the behavior:

1. Use binding.pry in a file

Expected behavior
Pry to work as it previously did

Screenshots

before_session hook failed: UncaughtThrowError: uncaught throw :jard_control_flow
/Users/scott/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/bundler/gems/ruby_jard-c794d14072ed/lib/ruby_jard/control_flow.rb:53:in `throw'

[0x2c7]

This issue is fixed in #41. You can now use one of binding.pry, byebug, debugger, jard commands depending your preference. The limitation is that after jard is first triggered, the backward compatibility is not guranteed anymore. The reason is that after Jard starts, it takes over internal states of Pry and Byebug. So, byebug and pry are not awared of external changes, and won't work as expected. If Jard doesn't start, they are fine.

def test
  jard
  sleep 0
  byebug # It triggers jard interfaces
  sleep 0
  binding.pry # Broken
end