better support for zero-volume ranges #447
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e1 composed of empty tiles only
evaleev
force-pushed
the
evaleev/feature/better-zero-extent-support
branch
from
6714078 to
9e07280
Compare
…range and w/ nonzero-volume contraction range producing zero-volume result
evaleev
force-pushed
the
evaleev/feature/better-zero-extent-support
branch
from
9e07280 to
087202a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
to simplify composition it would be useful to handle the corner case of zero-volume objects automatically ... this attempt to do that by adding support for
TiledRange1and their use inTiledRangeBlockRangeSparseShapewith for zero-volumeRangeTensorwith zero-volume rangeDistArrays