Antoine Fabri

from #16 : rig_in_namespace(pkg::foo, pkg:::bar)

`c("boomer_rigged", "function")` So we can recognized them easily. * original environment is set as an attribute * printing method will show it's rigged, and mention original environment/namespace * is_rigged function...

hopefully we can find a simpler example : 

From: #40 We might signal it when we override a variable accessible in a parent env, i.e. signal if exists("var") && !exists("var", exec_env)

When rigging a function, offer to wrap its function arguments

1

Now function arguments will be ignored :  I don't think there's a way to deal with this automatically, but if we `wrap()` `FUN` then we're good :  Maybe...

Explore intermediate steps using View or a webpage ?

2

Using View is a hack but would still be helpful, We'd call `boom(subset(head(mtcars, 1 + 1), qsec > 17), view = TRUE)` and have this happen, simulated here by :...

With a minor tweak implemented in https://github.com/moodymudskipper/boomer/tree/xml-experiment we can alter the output so it can be easily collapsed/expanded in an xml editor : ``` boom(subset(head(mtcars, 2), qsec > 17)) #>...

boom to dedicated rstudio tab?

2

just like the addin for `devtools::test()` prints to the "build" tab. It would make it easier to browse long input and not "pollute" the console. Not sure if RStudio offers...

boom recursively to error

2

We would have a function similar to rig but : * it rigs recursively the functions we find in the body * it doesn't print the boom output right away...

For instance I might want to "fork" a function, and copy needed unexported functions, but not the exported ones. How would this work ?