-
-
Notifications
You must be signed in to change notification settings - Fork 42
Concatenate trajectories #50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Also, the verb should be intuitive alone, because we may want to do the following: t0 <- ...
t1 <- ...
t2 <- ...
t3 <- concatenate(t0, t1, t2) And ?? concatenate
base::cat Concatenate and Print
base::paste Concatenate Strings
crayon::%+% Concatenate character vectors
grid::gPath Concatenate Grob Names
grid::vpPath Concatenate Viewport Names
igraph::c.igraph.es Concatenate edge sequences
igraph::c.igraph.vs Concatenate vertex sequences
NMF::c,NMF-method Concatenating NMF Models
stringi::%s+% Concatenate Two Character Vectors
stringi::stri_c Concatenate Character Vectors
stringr::str_dup Duplicate and concatenate strings within a
character vector. It seems there is no agreement on this. 😄 |
What about |
It's a good option. I would prefer something shorter, but it's difficult to be intuitive, cross-compatible with other packages and also concise. |
What about simply "join" (only present in plyr, which should be replace by dplyr, or "tjoin" to avoid the overlapping), "blend", "bind" (or "tbind", to mimic "rbind" and "cbind"), "connect", "link", "plug", "tie"...? |
|
A new verb is needed (for instance,
include
) so the following:should be equivalent to this:
The text was updated successfully, but these errors were encountered: