You recently learned about CLR 4's support for type equivalence in a
conversation right here on C9 with Raja Krishnaswamy and Jesse Kaplan
. The idea of type equivalence and its potential usefulness beyond simplifying and de-bloating COM interop that employs Interop Assemblies (CLR 4's No-PIA feature) led to the need to sit
down with Raja and Vance Morrison to really dig into the thinking behind the technology. How does type equivalence actually work? What are the semantics and why? In the VS 2010 timeframe, what should developers expect to be able to do with this new programming
abstraction? What types make sense to mark as equivalent? Why? Where does Type Embedding fit into this picture and what role does the compiler play in the No-PIA dance? What impact may this have on the future of managed-to-managed type "interop"? What's the
story here? What's next?
This is a great conversation with the primary minds behind type equivalence support in CLR 4. Enjoy.