You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unlike the tokens() sequence, where we always end with tokens.tokens(), dfm() does not end with dfm.dfm(). When verbose = TRUE, we don't get the ending.
Yes I very much like the elapsed time and closing message. It tells us something about the timings and sequence, good for diagnostics and for some users who want to know the precise sequences and/or timing without wrapping the function, it's useful.
Have you ever really used the elapsed time for diagnosis? I don't think so, because elapsed time for single execution doesn't mean anything. When we want to find slow functions, we use profvis::profvis().
I like this part
...starting tokenization
...preserving hyphens
...preserving social media tags (#, @)
...tokenizing 1 of 1 blocks
...segmenting tokens
...serializing tokens 10062 unique types
...removing separators, punctuation, symbols, numbers
Unlike the
tokens()
sequence, where we always end withtokens.tokens()
,dfm()
does not end withdfm.dfm()
. Whenverbose = TRUE
, we don't get the ending.Should look like:
but instead we don't see the final two/three lines:
The text was updated successfully, but these errors were encountered: