[r] Handle numeric coords
better in SOMASparseNDArray$read()
#3145
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix bug in handling of numeric coordinates when reading a sparse array. Now, always cast any integerish value to
bit64::integer64
(casting abit64::integer64
to abit64::integer64
is a no-op). Also strengthen value checking ofcoords
tocoords
to be a list ofNULL
or positive, finite, integerish valuescoords
to have a lengthcoords
to be a list of lengtharray$dimnames()
or be named witharray$dimnames()
NULLs
fromcoords
; ifcoords
is allNULL
, convert toNULL
Modified SOMA methods:
SOMANDArrayBase$private$.convert_coords()
: cast all integerish values tobit64::integer64
; strengthen value checking ofcoords
SC-57096