push the formatter up to the Route object
do not mutate parameters, let the caller do mutations
make variable name more clear
reduce object allocations

Example:

x = [1,2,3,4]
y = [3,2,1]

def test x, y
  hash = {}
  x.zip(y) { |k,v| hash[k] = v }
  hash
end

def test2 x, y
  Hash[x.zip(y)]
end

def test3 x, y
  x.zip(y).each_with_object({}) { |(k,v),hash| hash[k] = v }
end

def stat num
  start = GC.stat(:total_allocated_object)
  num.times { yield }
  total_obj_count = GC.stat(:total_allocated_object) - start
  puts "#{total_obj_count / num} allocations per call"
end

stat(100) { test(x,y) }
stat(100) { test2(x,y) }
stat(100) { test3(x,y) }

__END__
2 allocations per call
7 allocations per call
8 allocations per call
reuse path formatter from the non-optimized path.

The optimized and non-optimized path share more code now without
significant performance degretation
Add `force` option to `remove_column` for ignoring a missing column

sometimes you don't know if a previous migration ran, so it's useful
to unconditionally remove a column