{"comment":{"user":{"login":"todb-r7","id":1170909,"url":"https://api.github.com/users/todb-r7","avatar_url":"https://secure.gravatar.com/avatar/777bcd9397ea40f75ccd1023c8779257?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"777bcd9397ea40f75ccd1023c8779257"},"created_at":"2011-12-24T20:15:48Z","path":null,"updated_at":"2011-12-24T20:15:48Z","id":819644,"html_url":"https://github.com/rapid7/metasploit-framework/commit/3fe076bcd6#commitcomment-819644","position":null,"body":"Is there any reason at all to not simply monkeypatch NilClass? This class of error comes up a lot, and can be avoided with:\r\n\r\n    class NilClass; def empty?; true; end; end\r\n\r\nI can't think of any String#empty?() or Array#empty?() or Hash#empty?() test where this wouldn't be expected behavior if you get a nil.\r\n\r\nIn fact, I'll open a pull request for it, just to see if anyone shoots it down.\r\n\r\n","url":"https://api.github.com/repos/rapid7/metasploit-framework/comments/819644","line":null,"commit_id":"3fe076bcd66fc89def6bc95ea3cecd3c5e25bbd7"}}