Which parts of this project should go to imglib2 core?

[hanslovsky]

Many of the classes and interfaces in this project could be added to imglib2 core. Essentially, all packages that are not named unsafe plus most of net.imglib2.img.unsafe. The classes in net.imglib2.img.unsafe should be renamed from Unsafe<...> to LongAccess<...>.

This would leave only a small portion of the classes in imglib2-unsafe but these classes would all make use of sun.misc.Unsafe.

License headers and JavaDoc will need to be adjusted before moving any of the classes to imglib2 core.

Opinions? @axtimwalde @tpietzsch

[axtimwalde]

@hanslovsky and @tpietzsch and @StephanPreibisch I would prefer to add the long access methods to https://github.com/imglib/imglib2/tree/master/src/main/java/net/imglib2/img/basictypeaccess
and default them to their int counterparts. There is no guarantee for int access either that a particular int is available. Opinions?

[hanslovsky]

I think that adding these methods and defaulting to their int counterpart is reasonable. I agree that it is the caller's responsibility to provide appropriate accesses. If necessary, callers can add their own validity checks for their access/images.

In addition, I think that what is currently called UnsafeImg and related classes should be added to imglib2 core as LongAccessImg (or similar name).

Updated:
As a consequence of unifying basictypeaccess and LongAccess, would that mean that NativeType will be changed to be accessible through long index? As with the access, the long access methods could default to their respective int counterparts.