Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split IterableRegion #70

Closed
tpietzsch opened this issue Mar 26, 2024 · 0 comments
Closed

Split IterableRegion #70

tpietzsch opened this issue Mar 26, 2024 · 0 comments
Assignees

Comments

@tpietzsch
Copy link
Member

Currently, IterableRegion implements both RandomAccessibleInterval<BooleanType> and IterableInterval<Void>.

The idea is that if you have a RandomAccess, it will be true inside the region, and false outside. When you iterate you only want to visit the inside pixels (where the RA would be true). Therefore IterableInterval<Void>, not BooleanType.

It seemed at one point neat (albeit confusing) to implement this by inheriting Accessibles of different Type.
With imglib/imglib2#312 this will no longer be possible.
IterableRegion.getType() cannot return both Void and BooleanType.

Therefore, the "inside IterableInterval" should become a separate thing. maybe by adding a method IterableInterval<Void> inside().

@tpietzsch tpietzsch self-assigned this Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant