On Wednesday, 30 August 2017 at 14:46:12 UTC, Kagamin wrote:
https://dpaste.dzfl.pl/f7c5fc49d80f Like this. If you need
locking, write another mixin, it's just a very small
convenience wrapper.
I don't understand how this helps.
-What if I want an event to lock a shared mutex of the enclosing
object, without storing a pointer to that mutex inside the event
itself (and every single other event in the object)?
-What if I want an event to call a method of the enclosing object
when a handler is added (without keeping a pointer to it inside
the actual event)?
Please let me know if these questions are unclear. I stated these
concerns in the original post, and they have yet to even be
acknowledged by any of the responses here - so I'm finding this a
bit confusing at this point.
