Search Results

Scala allows this and calls the resulting type a Compound Type. Your example would look something like this in Scala: def seekAndRead(stream: IReaderStream with ISeekable) { stream.seek(5) // OK …

Conditional compilation effectively creates multiple versions of the code base. That's exactly the purpose of version control branches. The other alternative is put whatever code needs to vary in its …

Addition of many elements to the end is O(m + logn), where m is the number of elements to be added. These operations would be O(n + m), and if m = n then they are almost as fast as addition to the …

From your comments it seems you have something like this: Send(Data data, Address address, A a, B b, C c) { ... } Send(Data data, Address address, A a, D d, E e, F f) { ... } Send(Data data, Addres …

This is fairly common in ML-style languages like Standard ML/OCaml/F#/Haskell where it's much easier to create the wrapper types. It provides you with two benefits: It allows a piece of code to enfo …

Your first link does address the issue - it's laziness combined with side effects that is problematic, because the order of side effects matters. For pure computations, the main thing that changes is …

Helper classes can be an organizational anti-pattern when you have some generic Helpers file where you dump every single miscellaneous static function all your projects have ever used. Don't do that. …

There is a deeper issue here: the fact that C# and Java insist most/all types must be distinguishable by name rather than structure: e.g. class MyPoint2D and class YourPoint2D are separate types even …

It was done because it's the correct thing to do. The fact is that allowing all methods to be overridden is wrong; it leads to the fragile base class problem, where you have no way of telling if a cha …

I don't do much C# development but it seems to me you could define an attribute and apply it to all such classes. You could then give a thorough description of what restrictions that imposes on classe …

You can't. That's the thing about interfaces - they allow anyone to implement them at any time. There's an infinite number of potential implementations for your interface, and you can't force any of t …

A simple solution would be to make them immutable and produce new world objects for the next world state. This gives the Level complete control over the world's state without allowing objects to inter …

It seems to me on 2nd through that it's meant to be a class that should hold state, and not know how to call out to the .NET Framework to find info. Spot on. What you have is just a data containe …

Disclaimer: My C# experience is probably less than 8 hours total so the syntax that follows may not be accurate. So, somewhere between Device1.Method1; and Device2.Method3; When switching between …

It seems like the presentation and data should be defined in separate classes, but I can't think of a good way to do this while maintaining the ability to traverse the tree. Any suggestions? The …