Skip to content
New issue

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

A little bit of state? #95

Open
yjunechoe opened this issue Dec 7, 2022 · 0 comments
Open

A little bit of state? #95

yjunechoe opened this issue Dec 7, 2022 · 0 comments

Comments

@yjunechoe
Copy link
Owner

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.

Reference: https://twitter.com/tylermorganwall/status/1559619197042401282?s=20&t=mC9oyiZJ15soeVNszZmfHw

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant