boomer
boomer copied to clipboard
turn on boomer while browsing ?
If we're browsing in a function's body we can know the function's body from sys.call() and we can stitch an environment with shims right between it's closure env and its namespace, so I think this can work ?
This would be less verbose than going all in with boomer, and we wouldn't to set things up with rig_in_namespace beforehand.
Maybe a function with no arg called rig_local()
?
on.exit, we undo all the environment sorcery
What about boom_on() / boom_off() ? Also I think no action is needed on exit, we generally don't care about this env anymore and the GC will take care of it. I think this might even work in the global env and would be a very helpful feature