It’s also possible I miscounted the number of strings that become garbage in my example – the important thing is that string operations generate lots of garbage in places that you may not expect…

Glad you liked the article anyway!

Also I think the string concat example would only generate 3 garbage strings because of string interning.

To Filip:
structs can indeed implement interfaces, but if you use them through the IF then boxing (and possible garbage) will occur.

I have a couple of nit-picking comments:

“Second, it’s not completely accurate to say that value types never generate garbage. They can, of course, contain reference members, in which case creating a new struct object can indirectly create a new class object, which generates garbage exactly as though you’d created the class object yourself. It’s fair to say that this is a slightly unusual thing to do (I’m not sure I can think of an example?) but it’s entirely legal and something to watch out for.”

Well, you will never indirectly create a new class object by creating a struct that contains reference members, unless you use a specific non-default struct constructor that does that, and since you can’t override the default struct constructor it will probably not happen unless you did want it to happen!

Also, it’s not entirely correct to say that value types cannot inherit at all – structs can can implement interfaces

Waiting for a new post – keep it up!

Kostas