I suggest there is actually quite a lot to know about piping, albeit you can
use it fine while knowing little.
For those who can happily write complex lines of code containing nested
function calls and never have to explain it to anyone, feel free. I can do that
and sometimes months later I onl
I agree with you (I think we may be similarly aged), but there is the
`magrittr::debug_pipe()` function, which can be inserted anywhere into
either kind of pipe. It will call `debug()` at that point, and let you
examine the current value, before passing it on to the next entry.
You can't sing
Hi, Duncan:
On 6/29/24 17:24, Duncan Murdoch wrote:
Yes. I'm not yet facile with "|>", but I'm learning.
Spencer Graves
There's very little to know. This:
x |> f() |> g()
is just a different way of writing
g(f(x))
If f() or g() have extra arguments, just add th
Yes. I'm not yet facile with "|>", but I'm learning.
Spencer Graves
There's very little to know. This:
x |> f() |> g()
is just a different way of writing
g(f(x))
If f() or g() have extra arguments, just add them afterwards:
x |> f(a = 1) |> g(b = 2)
i
Hi, Rui et al.:
On 6/29/24 14:24, Rui Barradas wrote:
Às 17:02 de 28/06/2024, Spencer Graves escreveu:
Hello, All:
I'm getting strange errors with write.csv with some objects of
class c('findFn', 'data.frame'). Consider the following:
df1 <- data.frame(x=1)
class(df1) <- c('findFn
Às 17:02 de 28/06/2024, Spencer Graves escreveu:
Hello, All:
I'm getting strange errors with write.csv with some objects of
class c('findFn', 'data.frame'). Consider the following:
df1 <- data.frame(x=1)
class(df1) <- c('findFn', 'data.frame')
write.csv(df1, 'df1.csv')
# Error in x$P
