This recently became a warning, and I am not sure why. Yes, in the overlap
case, that might be something to worry about. But a perfectly reasonable
use case of merge,Seqinfo is to merge two disjoint sets of seqlevels. Now
we're forced to use suppressWarnings() for that.
Michael
[[alternat
Hi Michael,
On 10/12/2014 02:02 PM, Michael Lawrence wrote:
This recently became a warning, and I am not sure why. Yes, in the overlap
case, that might be something to worry about. But a perfectly reasonable
use case of merge,Seqinfo is to merge two disjoint sets of seqlevels. Now
we're forced t
But the behavior has changed for this case:
merge(Seqinfo("chr1"), Seqinfo())
Before it was "each has seqlevels not in the other" but now it is "these
two sets are disjoint". Subtle difference, but I think it's important?
On Sun, Oct 12, 2014 at 11:46 PM, Hervé Pagès wrote:
> Hi Michael,
>
>
On 10/13/2014 07:45 AM, Michael Lawrence wrote:
But the behavior has changed for this case:
merge(Seqinfo("chr1"), Seqinfo())
Before it was "each has seqlevels not in the other" but now it is "these
two sets are disjoint". Subtle difference, but I think it's important?
What has changed is tha
