eLobato (Daniel Lobato Garcia)
- Login: eLobato
- Email: elobatocs@gmail.com
- Registered on: 05/12/2013
- Last sign in: 02/05/2016
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 1 | 1 |
| Reported issues | 0 | 3 | 3 |
Activity
02/05/2016
-
12:17 PM Ruby Bug #12054 (Closed): Remove block from Logger.add as it's not needed
- Logger add (lib/logger.rb) takes as arguments severity, message, progname and &block
The method runs the block through yield. In this case, we can just omit the argument and we'd be saving the instantiation of a new proc object (see h...
05/27/2013
-
08:10 AM Ruby Feature #8453 (Closed): Implement Struct.map
- http://ruby-doc.org/core-2.0/Struct.html does not contain any 'map' like method, I imagine given 'each' and 'select' are available it's probably not too hard to implement.
As always I'm 100% open to contribute so if you deem this nec...
05/26/2013
-
03:02 AM Ruby Feature #8393: A class who's parent class is in a module can go wrong if files are required in the wrong order
- Fair point rkh, feel free to close this unless there is something to avoid printing lots of warnings.
05/16/2013
-
12:16 AM Ruby Feature #8393: A class who's parent class is in a module can go wrong if files are required in the wrong order
- This error showed up in a Rails app, on my code I had two different files (ProxyAPI::Resource and ProxyAPI::BMC < Resource), and somehow there was a separated Resource class defined by a loaded gem. Then ProxyAPI::BMC was inheriting from...
05/12/2013
-
05:41 PM Ruby Feature #8393: A class who's parent class is in a module can go wrong if files are required in the wrong order
- jeremyevans0: That's what I did when I found a problem caused by this on production code. Nonetheless you have to take into account that sometimes the order of the requires is not something you control.
nobu: In order to get these re... -
09:39 AM Ruby Feature #8393 (Rejected): A class who's parent class is in a module can go wrong if files are required in the wrong order
- Hi,
I have found that inheritance is not done properly in a certain case. Let's say we have the following files:
--------------
animal.rb -
class Animal
def bark
puts 'fuck.'
end
end
dog.rb -
module Bark
...