There are a number of arguments in the foverlaps() function that are not yet implemented:
Along with a few requested features:
There will be a lesson on the foverlaps() function in the DataCamp course on joins, so I'm wanting to gauge whether its worth trying to implement these features before the course is released. Are there obvious technical barriers that have prevented these features from being implemented? Or has there been a lack of interest from the community and developers, e.g. given the availability of GenomicRanges?
There are a number of arguments in the
foverlaps()function that are not yet implemented:type = "equal"- [FR] foverlaps type="equal" implementation #3416maxgapminoverlapAlong with a few requested features:
minoverlapfoverlaps()should work withoutsetkey()beforehandfoverlaps()could work with factor levelsThere will be a lesson on the
foverlaps()function in the DataCamp course on joins, so I'm wanting to gauge whether its worth trying to implement these features before the course is released. Are there obvious technical barriers that have prevented these features from being implemented? Or has there been a lack of interest from the community and developers, e.g. given the availability ofGenomicRanges?