Default Walker subclasses to using Visitor<SubType> (#921)

Most module walkers use PostWalker<T, Visitor<T>>, let that pattern be
expressed as simply PostWalker<T>

1 files changed, 2 insertions, 2 deletions

diff --git a/src/passes/PickLoadSigns.cpp b/src/passes/PickLoadSigns.cpp
index 6e44fddfe..6ead0cc4e 100644
--- a/src/passes/PickLoadSigns.cpp
+++ b/src/passes/PickLoadSigns.cpp
@@ -25,7 +25,7 @@ namespace wasm {
 // help remove the most sign/unsign operations
 // unsigned, then it could be either
 
-struct PickLoadSigns : public WalkerPass<ExpressionStackWalker<PickLoadSigns, Visitor<PickLoadSigns>>> {
+struct PickLoadSigns : public WalkerPass<ExpressionStackWalker<PickLoadSigns>> {
   bool isFunctionParallel() override { return true; }
 
   Pass* create() override { return new PickLoadSigns; }
@@ -45,7 +45,7 @@ struct PickLoadSigns : public WalkerPass<ExpressionStackWalker<PickLoadSigns, Vi
     // prepare
     usages.resize(func->getNumLocals());
     // walk
-    ExpressionStackWalker<PickLoadSigns, Visitor<PickLoadSigns>>::doWalkFunction(func);
+    ExpressionStackWalker<PickLoadSigns>::doWalkFunction(func);
     // optimize based on the info we saw
     for (auto& pair : loads) {
       auto* load = pair.first;