[mlir][sparse] Updating `Merger::foreachTensorLoopId` to take `LatPointId`
authorwren romano <2998727+wrengr@users.noreply.github.com>
Tue, 14 Mar 2023 20:00:29 +0000 (13:00 -0700)
committerwren romano <2998727+wrengr@users.noreply.github.com>
Wed, 15 Mar 2023 19:27:47 +0000 (12:27 -0700)
commitb60de1dfcc15d9505de958fe160b45bea11286f2
tree40697bcba29181812bf301b0666ee31e80a83118
parent73a01952b52c3210ca5d229ea18be8fedf1a8b6c
[mlir][sparse] Updating `Merger::foreachTensorLoopId` to take `LatPointId`

Since all callsites of `foreachTensorLoopId` would simply look up the `LatPointId` to extract its `BitVector`, it's cleaner to let the `Merger` handle that instead.  This seems to better capture the intent of the `foreachTensorLoopId` method, and improves decoupling (since it removes a place that leaks the implementation detail that we use `BitVector`).

Reviewed By: aartbik

Differential Revision: https://reviews.llvm.org/D146082
mlir/include/mlir/Dialect/SparseTensor/Utils/Merger.h
mlir/lib/Dialect/SparseTensor/Transforms/Sparsification.cpp