Antoine Fabri

Seems that it should be simple but I can't get it to work. * ran `usethis::use_c()` * created C and R functions * ran `pkgbuild::compile_dll(force = TRUE, register_routines = TRUE)`...

meanwhile b2539c0bfba2567d15d12f716b802961c0e4847b prints the message early so it doesn't clutter the output :  changing milestone since we can live with that

It we give a special treatment to `%>%` we'll still have the same issue with the native pipe and I'm not sure if we could handle it then, the native...

Could be `Inf` but right now I feel 10 (20 chars) might be good. We might need to play around with it.

With #40 we might be able to test if the argument is a function once it's evaluated, then we'd wrap it, it doesn't need to be optional and would be...

see also https://github.com/moodymudskipper/boomer/issues/32

Consider the idea of a shiny app or html report for compatibility with VS Code and other IDEs

https://github.com/moodymudskipper/boomer/issues/32 is probably a better idea

We might also boom recursively to a printed message, using regex. https://twitter.com/antoine_fabri/status/1398012181174759433 The default behavior would be similar as in OP, so a step further than what the tweet hints...

A first step is just to rig recursively, it's in fact very easy to draft, just `rig` and `wrap` where we previously just used `wrap`, with an exception for primitives,...