Delegate method privately called from delegate itself?
One has established design patterns so ingrained in their brain, that when sometimes somebody does something unexpected, it is a revelation.
Delegate method privately called from delegate itself?
One has established design patterns so ingrained in their brain, that when sometimes somebody does something unexpected, it is a revelation.
Delegate method privately called from delegate itself?
One has established design patterns so ingrained in their brain, that when sometimes somebody does something unexpected, it is a revelation.
Generic delegates (C#) in Scala?
I wanted to know if there is an equivalent of the C# generic delegates in Scala.
Is it ok for a for a View to dismiss itself?
Currently, I’m working on a project in which a view is dismissing itself.
Avoiding closures
I have a data structure in the form of a tree. Each node represents a cardboard box. The boxes can contain child boxes.
Why aren’t field-like events implemented as a list of delegates?
tl;dr: Why are field-like events implemented as a single delegate field? Wouldn’t it be more straight-forward to use a list of delegates, thereby eliminating the null special case and avoiding all the MulticastDelegate magic?
Why aren’t field-like events implemented as a list of delegates?
tl;dr: Why are field-like events implemented as a single delegate field? Wouldn’t it be more straight-forward to use a list of delegates, thereby eliminating the null special case and avoiding all the MulticastDelegate magic?
Many different classes that need similar functionality. Best approach?
I have many (at the moment around 30) different message classes in an application I am creating. Each of these messages need to be serialized and deserialized. However, the process of serializing and deserializing is mostly unique to each class (the format of the serialized message is specified in a document, and says which bits in the message goes where), but some are pretty straight forward and use the same process.