I ran into this pattern when converting elementwise ops like
addf %arg0, %arg : tensor<?xf32> to linalg. Redundant arguments can
also easily arise from linalg-fusion-for-tensor-ops.
Also, fix some small bugs in the logic in
LinalgStructuredOpsInterface.td.
I would avoid spreading the implicit logic.
As we discussed offline, tile on tensors will require putting even pointwise ops in "init_tensor form".
Would {base, base + getNumInitTensors()} work?