Just a really quick one today… What’s the point of this code? Does it have any point at all? public static class Extensions {     public static void Add<T>(this ICollection<T> source, T item)     {         source.Add(item);     } } Bonus marks if you can work out what made me think about it. I suggest you ROT-13 answers to […]

It's been a scandalously long time since I've blogged about C#, and now that the first C# 6 preview bits are available, that feels like exactly the right thing to set the keys clacking again. Don't expect anything massively insightful from me just yet; I'd heard Mads and Dustin (individually) talk about some new features of C# 6 at conferences, but this is the first opportunity I've had to play with the bits. There are more features to come, and I suspect that the ones we've got aren't in quite the shape t[...]

It’s been a scandalously long time since I’ve blogged about C#, and now that the first C# 6 preview bits are available, that feels like exactly the right thing to set the keys clacking again. Don’t expect anything massively insightful from me just yet; I’d heard Mads and Dustin (individually) talk about some new features […]

I was recently directed to an article on "tiny types" - an approach to static typing which introduces distinct types for the sake of code clarity, rather than to add particular behaviour to each type. As I understand it, they're like type aliases with no conversions between the various types. (Unlike plain aliases, an object is genuinely an instance of the relevant tiny type - it doesn't have "alias erasure" as a language-based solution could easily do.) I like the idea, and wish it were better supported [...]

I was recently directed to an article on "tiny types" – an approach to static typing which introduces distinct types for the sake of code clarity, rather than to add particular behaviour to each type. As I understand it, they’re like type aliases with no conversions between the various types. (Unlike plain aliases, an object […]