Re:Announcing .NET Framework 4.6
by maxlybbert on Tuesday July 21, 2015 @11:00PM
(#9927501)
I recognize that this particular change is meant as a convenience. But I'm not the person who put the exclamation mark in the part that I quoted from the article. And it makes me laugh that one feature they specifically call out is the ability to do what programming languages could do in, say, 1958 ( https://en.wikipedia.org/wiki/ALGOL_58 ).
Regardless, this change is very handy. Even if "everything must go in a class" is a bad idea (I think it's fine), the end result of this change, from the library consumer's standpoint, is the same as having functions defined outside a class but within a namespace. It's a great pragmatic change that doesn't rock the boat much.
In line with that are the other mostly minor but time saving changes like simplified null coalescing.
In previous versions this looks like: Not a huge change, but a very handy one to have.