Fix Subarray::add_point_ranges_var
to use the appropriate variable data Range
constructor.
#5560
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.
In #5490,
Subarray::add_point_ranges_var
was introduced as a user-friendly alternative to avoid the need to manually iterate and construct(point, point)
tuples for each query point. However, the initial implementation was using aRange
constructor intended for fixed-sized data. This was incorrect for variable-sized dimensions since it didn't utilize the appropriateset_range_var()
method, which is responsible for correctly setting internal attributes such asvar_size_
.Additionally, the test for this functionality didn't use the correct getter for retrieving variable-sized ranges from the subarray.
TYPE: BUG
DESC: Fix
Subarray::add_point_ranges_var
to use the appropriate variable dataRange
constructor.