Haha, I think I posted on that discussion asking for this same thing back then, too.
My main concern is to introduce another mechanism where functions are > dynamically added to modules. That's a very important consideration I had overlooked entirely. > It is also worth saying that we should generally stop defining default > implementations. This is also a fair point. I have worked on some projects with very particular needs, where all callbacks are truly mandatory (to conform to an interface) and not optional, but it is also trivial to provide default implementations for most by leveraging a few others, and rarely but strongly desirable to override some of those defaults. Clearly my experience in this arena has not been standard. I suppose another approach to this would be to try to augment defdelegate with support for some of the features it lacks that caused me to write my alternate version, so that piecing this sort of thing together within a __using__ macro requires much less glue without adding much surface area to the language. I'll look into the feasibility of instrumenting it with the option to copy @docs onto the delegate next time I'm frustrated enough to look into this again, and go from there. -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/99477891-9148-4b2c-9392-681da63a3e8c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
