Open weedySeaDragon opened 7 years ago
I came across this for a different angle. I've been running memory_profiler on a slow spec, and ruby-graphviz came up as one of the top gems allocating memory, and it came down to the symbolize_keys
implementation.
The
symbolize_keys
method inlib/core_ext.rb
is also defined with exactly the same name in the ActiveSupport gem inlib/active_support/core_ext/hash/keys.rb
Both add the method to
Hash
If both gems are used, this can result in warnings like this:
To avoid collisions, this method should only be defined if it doesn't already exist in Hash, or consider naming it something else. (preferably with a namespace or at least starting with
graphviz_
so it's unlikely to collide with any other gems.