We've talked about the retry keyword while discussing retrying after exceptions. Its little-known counterpart redo works similarly, but re-runs loop iterations instead of whole blocks.

The redo keyword

As we learned in the previous Academy article, retry lets you retry a piece of code in a block:

1begin
2  puts "Iteration"
3  raise
4rescue
5  retry
6end

This example prints the word "Iteration" to the console before raising an exception. The rescue blocks executes, which calls retry and starts the block again from the beginning. This results in our program endlessly printing Iteration. The redo keyword lets you achieve a similar effect when using loops. This is useful in situations where you need to retry while iterating for example.

110.times do |i|
2  puts "Iteration #{i}"
3  redo if i > 2
4end

This will print:

1$ ruby redo.rb
2Iteration 0
3Iteration 1
4Iteration 2
5Iteration 3
6Iteration 3
7Iteration 3
8...

Notice how the iteration count stays the same? It will step back execution to the start of the loop. This variant of the code using retry will print the exact same output:

110.times do |i|
2  begin
3    puts "Iteration #{i}"
4    raise if i > 2
5  rescue
6    retry
7  end
8end

You can use redo to implement retrying in a loop. In the next example we have a queue of jobs. They either return :success or :failure. We keep re-running the same iteration of the loop until the job succeeds.

1[job_1, job_2, job_3, job_4].each do |job|
2  redo unless job.call == :success
3end

The next keyword

If you want to move to the next iteration of the loop, as opposed to moving back to the start of the current one, you can use next.

110.times do |i|
2  puts "Iteration #{i}"
3  next if i > 2
4  puts "Iteration done"
5end

This will print:

1$ ruby next.rb
2Iteration 0
3Iteration done
4Iteration 1
5Iteration done
6Iteration 2
7Iteration done
8Iteration 3
9Iteration 4
10...

See how the iteration counter keeps incrementing? In most cases using next is what you want. Look at redo if you need a loop that runs an exact number of times or needs error handling when iterating over an array.

We hope you learned something new about redoing iterations in loops and would love to know what you thought of this article (or any of the other ones in the AppSignal Academy series). Please don't hesitate to let us know what you think, or if you have any Ruby subjects you'd like to learn more about.