Why is pry-nav discouraged for MRI?

Open justin808 opened this issue 4 years ago • 3 comments

Per the README:

Using MRI? We recommend break or pry-byebug instead!

pry-byebug has some issue with zeitwerk

Dec 16 '21 06:12 justin808

@justin808 honestly, not sure. Want to submit a PR to change this?

Most likely, https://github.com/ruby/debug is going to be the path forward, but can't hurt to update this for now.

Dec 16 '21 23:12 iloveitaly

Agreed with @iloveitaly that ruby/debug will be the path forward, but I originally put the recommendation because pry-nav uses set_trace_func which at the time was much slower than byebug. Ruby docs also say set_trace_func is obsolete. We could change to the TracePoint API and remove that recommendation.

Dec 17 '21 00:12 nixme

@iloveitaly Here you go: #42.

Dec 17 '21 01:12 justin808