Why is pry-nav discouraged for MRI?

Question

Why is pry-nav discouraged for MRI?

justin808 opened this issue 2 years ago · comments

Justin Gordon commented 2 years ago

Per the README:

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

pry-byebug has some issue with zeitwerk

Michael Bianco · Answer 1 · Fri Dec 17 2021 07:33:45 GMT+0800 (China Standard Time)

@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.

Gopal Patel · Answer 2 · Fri Dec 17 2021 08:46:02 GMT+0800 (China Standard Time)

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.

Justin Gordon · Answer 3 · Fri Dec 17 2021 09:04:57 GMT+0800 (China Standard Time)

@iloveitaly Here you go: #42.