4 ms·
> Async streams, indexers and ranges all rely on new framework types that will be part of .NET Standard 2.1. ... .NET Core 3.0 as well as Xamarin, Unity and Mo
by SideburnsOfDoom 8y ago
> Async streams, indexers and ranges all rely on new framework types that will be part of .NET Standard 2.1. ... .NET Core 3.0 as well as Xamarin, Unity and Mono will all implement .NET Standard 2.1, but .NET Framework 4.8 will not. This means that the types required to use these features won’t be available when you target C# 8.0 to .NET Framework 4.8.
We are approaching the point where .NET full framework becomes legacy, deprecated by .NET Core.
NetStandard 2.1 things like Span<T> are already in NETCore 2.1 now, but won't be in the next release of fullFramework, .NET Framework 4.8.
Which .NET Framework will they arrive in, and when, if ever? That question has not been answered, even with an approximation or roadmap.
- deleted 8y ago[deleted]
- merb 8y agowell to be fair, I would've prefered that they would kill mono...
- polskibus 8y agoThis is so bad - the language should be independent from the platform. They are breaking a lot of stability that was on the platform before, infuriating users and making people move away from .NET altogether. This is how you lose developers trust - who will trust them not to drop .NET Core soon in the future and start reimplementing again?