ENH: ufunc: Separate type resolution from loop selection

This change sets the stage for being able to produce much higher
performance loops by specializing based on any fixed strides. To do
this, type resolution must happen first to determine the dtypes,
then the iterator needs to be created, then finally the loop needs
to be selected for the given dtypes and the strides that will be
fixed throughout the iteration.

The way type resolution and loop selection where tied together before
precluded this possibility, but with the backwards-compatible design
change in this commit, such specializations will be possible in the future.

0 files changed, 0 insertions, 0 deletions