#receive! returns nil

[kornypoet]

Why is this? I want #receive! to return self like #update_attributes and .receive but it returns nil instead. What is the reasoning behind this? Also, why does #update_attributes NOT handle extra attributes? I have to work around all of these issues.

[mrflip]

Return of nil was intended to be a non-contract, which I then documented.
That was a stupid idea. Return self makes more sense, and should be put
into place.

Also +1 to update_attributes taking handle_extra_attributes

Overall I think we'd benefit from you doing a thoughtful review of the
gorillib contract -- basically read through the rdocs, flag things that are
mature with @api rdoc tag, highlight methods that seem unused or that
offer too much functionality.

flip

On Tue, Oct 2, 2012 at 9:10 AM, Travis Dempsey notifications@github.comwrote:

Why is this? I want #receive! to return self like #update_attributes and
.receive but it returns nil instead. What is the reasoning behind this?
Also, why does #update_attributes NOT handle extra attributes? I have to
work around all of these issues.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6.

infochimps.com - discover data

[temujin9]

+1 for Travis making gorillib more pro and less unpro.