Markus Schirp
Markus Schirp
@snusnu I think you need to reparse your quesition and outline it with code. Are you talking about a `super` or `zsuper` call in the generated initializer? Or an implementation...
@snusnu What about NOT calling super in the generated constructor all?
@snusnu Lets only add what we need. So lets drop `#remove` for now. And only add `#add`. Once we need `#remove` we can consider it, and than we also see...
The refactoring need would not be an issue from my POV. We could have a transition period where the old one still works but emits deprecated noticed. What I don't...
@dkubb I think the intent of this change is okay. But I fear we run into ordering issues with equalizer, concord, anima includes. Can we guard against overriding the memoized...
@dkubb IMHO: I'd be okay to issue a warning. If someone dislikes these warnings he can define their own `#hash` and friends, _than_ `import Adamantium` or dont use this library....
@dkubb Yeah. This will allow equalizer and similar libs to work without ANY knowlege about adamantium +1. I think this is the way to go.
@dkubb Maybe you should NOT memoize `#hash` and friends by default. Only if a method missing was detected!
@dkubb I meant `method_added`. Sorry obviousely NOT method missing ;)
@mbj Only disables adamantium when its a problem and only very fine grained. Example is deep freezing big JSON / YAML parsed deeply nested trees. For my business logic admantium...