From b15e2aec753cb6fc50b78ef540c29d501f38b09a Mon Sep 17 00:00:00 2001
From: Andy Ly <lyandy@google.com>
Date: Tue, 6 Aug 2019 20:48:29 -0700
Subject: [PATCH] Have ValueUseIterator template use OperandType instead of
 IROperand.

This was causing some issues using helper methods like llvm::make_early_inc_range on Value::getUses(), resulting in IROperand instead of OpOperand.

PiperOrigin-RevId: 262056425
---
 mlir/include/mlir/IR/UseDefLists.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mlir/include/mlir/IR/UseDefLists.h b/mlir/include/mlir/IR/UseDefLists.h
index d266935..fe0e9e0 100644
--- a/mlir/include/mlir/IR/UseDefLists.h
+++ b/mlir/include/mlir/IR/UseDefLists.h
@@ -197,7 +197,7 @@ public:
 /// An iterator over all uses of a ValueBase.
 template <typename OperandType>
 class ValueUseIterator
-    : public std::iterator<std::forward_iterator_tag, IROperand> {
+    : public std::iterator<std::forward_iterator_tag, OperandType> {
 public:
   ValueUseIterator() = default;
   explicit ValueUseIterator(OperandType *current) : current(current) {}
-- 
2.7.4