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
It's possible for the user to mistakenly pass a dataset twice to bed_intersect() when using the %>% operator. This happens when an intermediate function is called within the bed_intersect call. The data gets passed implicitly to the x argument, then secondly as a dots (...) argument. I'm not sure what options we have to detect this on our end, and for some users this might be a feature rather than a bug. The native pipe operator won't allow this, as the data/placeholder can't be passed twice.
It's possible for the user to mistakenly pass a dataset twice to bed_intersect() when using the %>% operator. This happens when an intermediate function is called within the bed_intersect call. The data gets passed implicitly to the
x
argument, then secondly as a dots (...
) argument. I'm not sure what options we have to detect this on our end, and for some users this might be a feature rather than a bug. The native pipe operator won't allow this, as the data/placeholder can't be passed twice.This doesn't happen with the native pipe, as you can't (implicitly or explicitly) pass the data twice.
Created on 2024-04-03 with reprex v2.1.0
The text was updated successfully, but these errors were encountered: