Changes to DicomValue API and sequences #353
Merged
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.
This makes some usability improvements to the core value API. The main changes here are the enum
DicomValue<I, P>
now has a different default for the type parameterP
(to the same value used by in-memory DICOM objects indicom_object
), and it uses struct definitions for data set sequences and pixel data fragment sequence, instead of declaring struct variants in the enum.I also took this opportunity to remove deprecated functions, adjust the error types returned in some methods, and increase test coverage a bit.
Summary
DicomValue
sequence variant fields to their own independent types (DataSetSequence
andPixelFragmentSequence
)P
toVec<u8>
(also aliased toInMemFragment
)Value::to_str
,Value::to_raw_str
,Value::to_bytes
CastValueError
toConvertValueError
PartialEq
forDicomValue
between data set items: recorded length is ignored, only items are compared.