why does trash exists?

[gregory]

"A Trash is a Dash that allows you to translate keys on initialization"

Why shouldn't we just include an extension for the key translation @mbleigh ?

class Person < Dash
  include Hashie::Extensions::Dash::PropretyTranslation

  property :id, transform_with: lambda { |v| v.to_i }
  property :created_at, from: :creation_date, with: lambda { |v| Time.parse(v) }
end 

[mbleigh]

There's some history here. Originally Hashie didn't have any mixins for its functionality, instead relying only on subclassing. At one point, my plan was for Hashie 2.0 to do away with the need for the subclassed hashes entirely, leaving them in for legacy and convenience but making them only the compilation of a few mixins. I ran into some bizarre circular calling issues and more or less abandoned that work, even though in-progress some of it had been committed to the master branch.

Since then, other maintainers have taken up the mantle and honestly I don't have a great idea of where anything in this project is right now. Suffice it to say that Trash may well be completely implemented by your snippet above (I'm not sure either way) but the reason it exists is because it was added to the library in the "pre-mixin" era.

[gregory]

That was 4years ago :) will see what i can do about that when i get some time! thx

[dblock]

@gregory If you replace the Trash implementation by the above, do all tests pass? Probably a good way to figure out whether we should kill it or not :)