re: Truth tables as Ruby Hashes VIEW POST

TOP OF THREAD FULL DISCUSSION
re: While this is clever, be careful when doing this in production code. That temporary object is used once and thrown away, only to be generated again...
 

That's a nice way of doing it Scott, it's cool to get different perspectives. You make a good point about re-generating objects too and this is certainly true in my example above. But, as I mention in the post, memoizing the Hash mitigates this problem :) gitlab.com/snippets/1791110

 

While that's better it still creates clutter in your object. A default inspect will show @h = ... even though that's not really relevant to that object. There's no reason to create this per-object, either, it doesn't change. That's why I recommend as a constant, out of the way and implicitly shared.

Also remember that months have commonly recognized numerical identifiers, there's no need to say "feb" when 2 will do.

code of conduct - report abuse