memoize and invalidation - backwards?
27 views
Skip to first unread message
Sam Grönblom
Feb 8, 2012, 10:29:14 PM2/8/12
to Ruby on Rails: Core
Maybe this is because I'm missing something but it seems to me that
asking users of a memoized method to know when the method needs to be
reloaded is a bit backwards. To me it seems like whoever is messing
with something that affects the results of the memoized function
should be the one that after doing its work should call something like
memoized_method(:reset). Thoughts?
asking users of a memoized method to know when the method needs to be
reloaded is a bit backwards. To me it seems like whoever is messing
with something that affects the results of the memoized function
should be the one that after doing its work should call something like
memoized_method(:reset). Thoughts?
Reply all
Reply to author
Forward
0 new messages