Method chaining and lazy evaluation in Ruby

http://jeffkreeftmeijer.com/2011/method-chaining-and-lazy-evaluation/

by joshuacc • 15 years ago

54 5 15 years ago

jarin• 15 years ago

This is a pretty good bite-size sampling of the workings of some of the nice things we take for granted in Rails (like AREL). Rspec is another one that's worth looking into:

http://stackoverflow.com/questions/3105755/ruby-metaprogramm...

jkreeftmeijer• 15 years ago

Thanks! I totally agree RSpec's a good library to dive into too. To understand how it works, I wrote Raptor (https://github.com/jeffkreeftmeijer/raptor) a while back. I might write about that too, sometime. :)

bphogan• 15 years ago

I really enjoyed that. It's something I wish I knew early in my Ruby programming experience. I've done similar things on my own but I really appreciated the approach taken here.

JoelMcCracken• 15 years ago

It seems obvious to me that this would be how to implement this. When I read his initial code, I immediately wondered why he wasn't returning self.

Maybe this familiarity comes with having spent enough time reading through the jQuery internals. Speaking of which, if you like this article, the classic "10 things I learned from the jQuery source" is great reading:

http://paulirish.com/2010/10-things-i-learned-from-the-jquer...

ddfreyne• 15 years ago

If I were implementing this, I would go for an implementation where my Criteria objects are immutable. To me, it seems that code like

    crit1 = Criteria.new.where(:name => 'Jeff')
    crit2 = crit1.where(:age => 19)

would result in two different criteria, which is not the case. “crit2 is the original criteria where age is 19” makes sense, but I would not expect that to update crit1.

I don’t mind mutability per se, but it needs to be clear what data is mutable and when it is mutated.

Method chaining and lazy evaluation in Ruby

Related Stories