Even more annoying if we're timing it, we could wrap the call but it's cumbersome :
my_log_function({
x <- foo(y)
})
I want :
log_next(message = "computing", fun = "foo")
x <- foo(y)
Would display the message first : "In progress: ..."
Then once computed : "... V" (with a tick mark emoji) along with time stamp and time
Just like with {progress} we should have a format, by default the message is the first line of code.
By default the fun is either of <-, =, control flow constructs, or { (so basically 95 % of calls we just miss side effects), we could also really do any next call by using the trick I used in {goto}, maybe better.
This might be done in {once}.
logging might be enabled by options, we can see how other logging packages do things. :
Maybe be smart detecting for loops and apply funs and have an optional progress bar for those (default to TRUE).
For while/repeat we can still show the start and elapsed time.
This pattern is annoying :
Even more annoying if we're timing it, we could wrap the call but it's cumbersome :
I want :
Just like with {progress} we should have a format, by default the message is the first line of code.
By default the
fun
is either of<-
,=
, control flow constructs, or { (so basically 95 % of calls we just miss side effects), we could also really do any next call by using the trick I used in {goto}, maybe better.This might be done in {once}.
logging might be enabled by options, we can see how other logging packages do things. :
Maybe be smart detecting for loops and apply funs and have an optional progress bar for those (default to TRUE). For while/repeat we can still show the start and elapsed time.
operations that rely on the stack might break.