Re:The Billy Baldwin of Conditional Assignment in Ruby
by MostAwesomeDude on Wednesday June 22, 2011 @12:29AM
(#2681730)
Python doesn't need it; the savings from not double-evaluating things aren't there. Additionally, Python lore is to expand this idiom to an if statement, for explicitness, especially in polymorphic situations where you actually want to check for "<expr> is None" rather than "bool(<expr>)". Both of these examples are Railsy; equivalent Djangoy statements in form validation would have to deal with None:
Because of Python's string immutability, there's no point to dodging the assignment; you're still going to incur new string creation anyway.
[ Parent
| on HN ]
Re:The Billy Baldwin of Conditional Assignment in Ruby
by mitchty on Wednesday June 22, 2011 @10:14AM
(#2683174)
I'm sort of torn on using these magic operators in Ruby, and i've used ruby since the 1.4 days.
For example this:
some_var &&= replace_var()
some_var ||= initialize_var()
versus a more conventional/idiomatic if: some_var = (some_var) ? replace_var() : initialize_var()
||= turns out to be rather useful as a general assign once operator, but i'm having a hard time justifying use of &&=. That and I find myself after learning Erlang to try to assign only once when possible to make debugging easier.While ||= isn't strictly needed, it makes assigning to class/module variables in a single line easier in general. I'm not sure I agree with the Python "always expand to an if statement" methodology though, it just seems like a bit of unneeded yak shaving. (note: i don't use rails so your post may be specific to web frameworks and I'm off my rocker, if so disregard. >.<)