Improve Variant and SafeArray implementations #100
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.
Safety:
safearray
: NowSafeArrayAccessor::new
andsafe_array_to_vec{_of_strings}
areunsafe
, as it is the caller's responsibility to pass valid arrays.SafeArrayAccessor
now exposes an iterator over the array (and not a slice), based on the data pointer+element count (vs the lower/upper bounds)Other changes:
Variant::from_variant
will now usewindows-rs
'sVARIANT::to_string