> I'm just curious why the change... and wondering if there is a way to > make it compatible with my full? implementation so I won't have to go > refactor tons of code.
The change was made to reduce the memory consumption and garbage generated when you have an explicit block parameter. However if it's breaking things we can look at reverting it. It was *meant* to be fully backwards compatible. If you can add a test for what you're doing, it'd make it easier for us to figure out the best way forward. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
