Rails Ruby on Rails → 2.x

Comments and changes to this ticket

• 

  Pratik August 5th, 2009 @ 02:42 PM

  • State changed from “new” to “wontfix”

  This looks interesting. But I'm not sure if this pattern belongs to the core or not. You should probably spark a discussion in the core ML - http://groups.google.com/group/rubyonrails-core

  Thanks.

• You flagged this item as spam.
  

  Luca Guidi August 6th, 2009 @ 02:32 PM

  Attached a patch for a more efficient implementation: http://gist.github.com/163274

  • 0001-Added-Enumerable-else-for-the-execution-of-alternati.patch 1.8 KB
• 

  Eloy Duran August 6th, 2009 @ 02:49 PM

  @Luca: In the docs you miss the 'do' keyword: “end.else” => “end.else do”. Besides that; verified and I like it! +1

• You flagged this item as spam.
  

  Luca Guidi August 6th, 2009 @ 03:02 PM

  Thanks Eloy, I just fixed the rdoc issue and added a couple of test cases.

  • 0001-Added-Enumerable-else-for-the-execution-of-alternati.patch 1.9 KB

• You flagged this item as spam.
  

  blatyo August 7th, 2009 @ 02:23 PM

  I could definitely see myself using something like this. I would definitely change the name from else though. It's bad practice to use keywords as method names and else provides no context when used by itself. +1 (with some changes)

• You flagged this item as spam.
  

  Luca Guidi August 7th, 2009 @ 02:43 PM

  @blatyo which name do you suggest?

• You flagged this item as spam.
  

  Paul August 7th, 2009 @ 03:24 PM

  i do not think the use of else is bad within this context. it reads nice:

  with.each do this end.else do that end

  using it "standalone" does not make much sense i.m.O.

  elements.else do
  ... end

  an

  if elememts.blank?
  ... end

  is and will be better - regardless of the naming of the method...

• You flagged this item as spam.
  

  Evgeniy Dolzhenko April 16th, 2010 @ 01:39 PM

  My take on it is: when_blank