The problem is what to do when a rowData field is not identical across cbind'd elements. Currently cbind throws an error, which is understandable (and safest) but inconvenient.
A more convenient approach would be to simply drop non-identical fields with a warning. This would allow people to proceed with cbinded results - most of the time, they won't even care that the fields are lost, given that it wouldn't make sense for them to be there anyway.
cbind already accommodates situations where the elements have non-identical rowData with non-overlapping names, so it doesn't seem much of a stretch to just drop fields instead of erroring.
Inspired by https://support.bioconductor.org/p/126722/.
The problem is what to do when a
rowDatafield is not identical acrosscbind'd elements. Currentlycbindthrows an error, which is understandable (and safest) but inconvenient.A more convenient approach would be to simply drop non-identical fields with a warning. This would allow people to proceed with
cbinded results - most of the time, they won't even care that the fields are lost, given that it wouldn't make sense for them to be there anyway.cbindalready accommodates situations where the elements have non-identicalrowDatawith non-overlapping names, so it doesn't seem much of a stretch to just drop fields instead of erroring.