Markus Schirp

I'd dislike this the `ast` gem dropping immutability. Dunno if that is proposed here. There are lots of patterns to associate data with immutable objects. Worst case you can use...

> Having worked on similar applications, I strongly suggest looking into a separate mutable structure that keeps e.g. variable metadata. Strong concur, this is what I'd do.

@akimd I personally am out of options to help, without seeing the actual source code. I could write up some source-to-source transformation, but the chance I hit your exact use...

Also for most tools: Repo = Website.

This is a bug I did not catched since I do not use mutable business objects. Will fix this soon. Thx for reporting!

Currently the validation error generation was dropped. I'll readd validation error message generation as decorators.

@tjchambers I suspect that there is a behavior change for ruby 2.4. I do not consider 2.4 stable enough yet to switch my clients code to it, as soon this...

@elskwid I think kwargs are better done in anima. I'm using kwargs in one of my commercial apps now and I think we should allow them there.

We have `include anima.add(:some, :attributes)` I think we should add `include concord.add(:foo, :bar)` for symetry. If we reference the superclasses metadata via calling `concord` and `anima` singleton methods its more...

@snusnu Why not? I'm generally a bit defensive adding features to this libs. For anima I cleanly saw the point. For concord I never had the use case.