3 ms·
> Kind of like how there isn't a C# 2005 standard Er... no. There is: it's just that C# stopped being published as an ISO Standard after version 2.0, and MS st
by DaiPlusPlus 5y ago
> Kind of like how there isn't a C# 2005 standard
Er... no. There is: it's just that C# stopped being published as an ISO Standard after version 2.0, and MS stopped publishing C# as an ECMA Standard a few years ago, but the C# language still has specifications and those specifications have version numbers - and those version numbers are used as compiler flags: `csc /langversion:7.3`, for example.
> But it's still OK to refer to C# 2005 as a thing.
"C# 2005" was C# 2.0, the last version with an ISO spec.
Currently we're on C# 9.0 in .NET 6. C# language spec versions and .NET releases are tied together as new language features have dependencies on BCL features (e.g. C# 8.0's `foreach-await` requires `IAsyncEnumerable` which was added in .NET Core 3: https://docs.microsoft.com/en-us/archive/msdn-magazine/2019/november/csharp-iterating-with-async-enumerables-in-csharp-8 https://docs.microsoft.com/en-us/archive/msdn-magazine/2019/...
That said, the C# language does enjoy relatively good evolution and progress that's almost as rapid as Swift's, and unlike, say, Java, which feels to me like it's progressing at half the speed of C#.