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
Hm, currently between() checks which values of x is between y and z (length=1 as it were before this commit). In that sense, if it has to be vectorised, then the Q we could instead ask is:
Is x between any of the ranges between y and z?
In essence, we could promote current vectorised behaviour to do even more -- true range join/subset. Will do and then close.
Submitted by: Michele Carriero; Assigned to: Nobody; R-Forge link
As implemented now
between(x, y[1], y[2], incbounds = TRUE)
%between%
has only a single upper and lower bound. Replacing its body withbetween(x, y[[1]], y[[2]], incbounds = TRUE)
would allow the current usage plus a vectorised usage. Like:
dt[ colA %between% list(colB, colC)]
The text was updated successfully, but these errors were encountered: