Comments

@Charles: I think Garrett Serack @fearthecowboy knows the problem, he retweeted one of those

ha, funny you talked about dx.h, because Kenny Kerr's reaction was like this:

https://twitter.com/kennykerr/status/327856228778770433

and one day before that

https://twitter.com/kennykerr/status/327588456962338816

maybe sometime the PCL will be the new 'regular'

maybe you can explain what GCLargeObjectHeapCompactionMode is next time.

Maoni is super !

what's next for Windows, Windows Server, Windows Azure, Visual Studio ...

what about XBox, inside the 'and more' ?

Hmm... waiting for Wesner Moise's update post about this:

http://wesnerm.blogs.com/net_undocumented/2013/03/immutable-collections-critique.html

Nice

If the MSR work you talked about is this
http://research.microsoft.com/apps/pubs/default.aspx?id=170528

then its very interesting to think about it, IIRC (could be wrong) the 'immutable' reference applies to the whole object graph can be reached from it, meaning a 'immutable' collection can't have mutable objects as elements !? so the pattern here is actually quite different.

That said, as far as I understand it, the algorithm itself should be perfectly suitable for immutable references, you just create an 'isolated' node, mutate it as you like, including let it point to the previous immuable tree nodes etc, then return it as an immutable reference, its exactly the 'builder' pattern and 'freeze'/consume pattern, and I think this kind of ability is exactly why the approach in that paper is better than previous works.

Happy Birthday !!!