@andrewthad suggested changing the naming conventions to use the more common assumption that people will import thing other than types qualified. I think it would probably be too disruptive to do that directly. But sharing (or even copying and pasting) code among the different array implementations would be much easier in that regime. I believe there is quite a lot of code that could be shared. That suggests an alternative approach: layer primitive on top of another package, in the same repository, that uses the other convention. primitive itself would just be a thin shell over the other package.
@andrewthad suggested changing the naming conventions to use the more common assumption that people will import thing other than types qualified. I think it would probably be too disruptive to do that directly. But sharing (or even copying and pasting) code among the different array implementations would be much easier in that regime. I believe there is quite a lot of code that could be shared. That suggests an alternative approach: layer
primitiveon top of another package, in the same repository, that uses the other convention.primitiveitself would just be a thin shell over the other package.