Is there a way to not force users to import IterableAccessor and BoundedIterableAccessor?

[uint]

@webmaster128

Having to import IterableAccessor and BoundedIterableAccessor is a bit annoying for standard functionality like iterations

My intuition is this would be hard to do, but maybe there are steps we can take here. Brainstorming pending.

[webmaster128]

One way this could work is to make the types in cw-storey a newtype instead of an alias. Then you can have e.g.

pub struct Column<T>(storey::containers::Column<T, crate::encoding::CwEncoding>);

and provide the best possible user experience for cw_storey::Column and keeping a lot of abstraction internal

[uint]

Sure, but that also increases the maintenance burden, sort of. I'm a bit hesitant there.