Open justin808 opened 2 years ago
@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.
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.
@iloveitaly Here you go: #42.
Why is pry-nav discouraged for MRI?
Per the README:
pry-byebug has some issue with zeitwerk