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
At this point {ggtrace} is probably going to continue developing against the cran direction, prioritizing features and convenience for interactive debugging uses,
Maybe another development to think about here is having a package environment. That refactors the tracedumps which are currently implemented as closures. It could also be a central place to manage internal variables like .ggtrace_placeholder. Additionally, workflow functions could assign into the package env as a way of tracking things like ._counter _ - I found the current implementation to be especially difficult for ggtrace() and with_ggtrace() which is why those don't expose have the ._counter_ feature yet.
At this point {ggtrace} is probably going to continue developing against the cran direction, prioritizing features and convenience for interactive debugging uses,
Maybe another development to think about here is having a package environment. That refactors the tracedumps which are currently implemented as closures. It could also be a central place to manage internal variables like
.ggtrace_placeholder
. Additionally, workflow functions could assign into the package env as a way of tracking things like._counter _
- I found the current implementation to be especially difficult forggtrace()
andwith_ggtrace()
which is why those don't expose have the._counter_
feature yet.Reference: https://twitter.com/tylermorganwall/status/1559619197042401282?s=20&t=mC9oyiZJ15soeVNszZmfHw
The text was updated successfully, but these errors were encountered: