We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently for power_assert testsuite, it depends on byebug:
power_assert/power_assert.gemspec
Line 26 in 297fa68
power_assert/test/trace_test.rb
Line 10 in 297fa68
So can I rely on byebug?
Why I am asking here is that
So I think if power_assert is going to use byebug, someone has to support byebug maintainership. Or can power_assert be switched to use debug gem?
The text was updated successfully, but these errors were encountered:
@deivid-rodriguez FYI
Sorry, something went wrong.
PowerAssert.trace depends on byebug, but I think this method is only used by my PoC gem pry-byebug-power_assert.
So I'll remove this feature. (At least for now. I might implement the same feature using debug.gem)
No branches or pull requests
Currently for power_assert testsuite, it depends on byebug:
power_assert/power_assert.gemspec
Line 26 in 297fa68
power_assert/test/trace_test.rb
Line 10 in 297fa68
So can I rely on byebug?
Why I am asking here is that
So I think if power_assert is going to use byebug, someone has to support byebug maintainership.
Or can power_assert be switched to use debug gem?
The text was updated successfully, but these errors were encountered: