You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Leaving calls like browser() in the code after the bug is fixed is a common mistake; most "finished" code (especially in packages) shouldn't need to call this.
I believe the same goes for debug(), undebug(), trace(), untrace(), and debugcall().
I think it would make sense for these to be in the default set of undesirable functions for undesirable_function_linter.
Any second thoughts?
The text was updated successfully, but these errors were encountered:
Leaving calls like
browser()
in the code after the bug is fixed is a common mistake; most "finished" code (especially in packages) shouldn't need to call this.I believe the same goes for
debug()
,undebug()
,trace()
,untrace()
, anddebugcall()
.I think it would make sense for these to be in the default set of undesirable functions for
undesirable_function_linter
.Any second thoughts?
The text was updated successfully, but these errors were encountered: