On Aug 12, 2013, at 7:25 PM, Amiel Martin wrote: > I like this idea and I would use it. > > My only suggestion would be to normally return a new instance of the proxy > object. This makes it easier to use this feature with immutable objects. > I know it would be possible to do this: > > class ProxyContainer < Struct.new(:brands) > delegate :select, to: :brands, return_value_of: 'self.class.new(result)' > # ... > end > > but it's not obvious that you could do this without reading through the > definition.
We already have a DSL for specifying the return value of a method: it's called RUBY. :) Snark aside, I think adding too many bells-and-whistles to `delegate` is not the best idea. If you really want custom behavior, why not make it clearer and just write the methods? At a minimum, code-as-string is kinda gross. --Matt Jones -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/groups/opt_out.
