Ruby, Rails and DoubleRenderErrors... Oh my!

There's a new "feature" that's been added in Rails 0.13.0 that is a bit of a hack to fix behavior that a lot of people didn't feel was correct. In Rails, you can actually call a redirect or render method and instead of returning immediately Rails will continue execution until it hits the end of the method or an explicit return.

I think the Rails developers did the right thing in adding the new exception, because almost all users expected that a render or redirect would immediately return - I know I did. It also affords any strange hacks out there that wanted this behavior to still achieve it by catching the exception and ignoring it. In any case, I'd agree that this behavior should have been built into the render and redirect actions from the beginning. I can't really think of any situation where you'd want to render/redirect and then continue to execute...