Nested resource constraints are applied incorrectly

When using nested resource id constraints the options are applied incorrectly because the implicit nested call occurs after the options have been pushed out to the scope, e.g:

 resources :lists, :id => /([A-Za-z0-9]{25})|default/ do
   resources :todos, :id => /\d+/
 end

Specifying the routes in full gives the correct results:

 resources :lists, :constraints => { :id => /([A-Za-z0-9]{25})|default/ } do
   nested do
     resources :todos, :constraints => { :id => /\d+/ }
   end
 end

The attached patch moves the nested call before the options are processed.