InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

C# Feature Focus: Co- and Contra-variance

Posted by Jonathan Allen on Oct 27, 2008

Sections
Development,
Architecture & Design
Topics
.NET ,
Language Design
Tags
C# 4 ,
C# ,
.NET Framework 4.0

In order to match Java and support J#, .NET arrays have always been co-variant. Unfortunately it was done so in an unsafe fashion, necessitating the need for runtime checks whenever storing values in an array. For .NET 2 and generics, neither co- nor contra-variance was supported.

.NET 4 will support safe co- and contra-variance on interfaces and delgates. In order to do this types in the interface can be marked with either an "in" or "out" modifier. If marked as out, the interface supports co-variance and the given type can only appear as a return type or read-only property. If marked in, the type can only appear as a parameter or set-only property.

This support is only for reference types, no variance is allowed on structures. Also, parameters passed by reference are not allowed. IEnumerable, IQueryable, Func, and Action are examples of primary interfaces and delegates that will be marked for variance support.

For more information on this see our article Covariance and Contravariance in .NET Generics and Eric Lippert's Co- and contra-variance: how do I convert a List(Of Apple) into a List(Of Fruit).

More Information by Jonathan Allen Posted
  1. Back to top

    More Information

    by Jonathan Allen

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.