corefxlab

Current plan is: https://github.com/dotnet/corefxlab/issues/2350

CoreCLR actively discussing introducing Utf8String type. https://github.com/dotnet/corefxlab/issues/2350

.NET is going to add UTF8 strings [1], though it remains to be seen how usable they will be given that all existing APIs take non-UTF8 strings. [1] https://github.com/dotnet/corefxlab/issues/2350

It is a path to enlightenment with multiple stops. :) Start with Joe Duffy blog posts about Midori architecture. http://joeduffyblog.com/2015/11/03/blogging-about-midori/ Then hop on to his talks. "Safe Systems Programming in C# and .NET" https://www.infoq.com/presentations/csharp-systems-programmi... "RustConf 2017 - Closing Keynote: Safe Systems Software and the Future of Computing by Joe Duffy" https://www.youtube.com/watch?v=EVm938gMWl0 Then you can watch "Inside .NET Native" from Channel 9 https://channel9.msdn.com/Shows/Going+Deep/Inside-NET-Native Finally there are the specs and related discussions that lead up to C# 7.3 design. https://github.com/dotnet/corefxlab/tree/master/docs/specs The TL;DR; version, basically async/await, the UWP AOT compiler, improved handling of value types, spans (aka slices), improved GC (TryStartNoGCReg

Maybe these? https://github.com/dotnet/corefxlab/blob/master/docs/specs/s...

Can someone update the link to https://github.com/dotnet/corefxlab/blob/49982d193b4853002a9...

It's getting easier with every release to not allocate, with things like ref returns and locals[1] and new types like Span<T>[2]. I think there are more things like that coming in the pipeline[3]. [1] https://github.com/dotnet/roslyn/issues/118 [2] https://github.com/dotnet/corefxlab/blob/master/docs/specs/s... [3] https://github.com/dotnet/roslyn/issues/10378

Currently they are playing with Span<> and Memory<> at CoreFX Labs, which make use of IDisposable, so they could at least partially support it at library level. https://github.com/dotnet/corefxlab https://github.com/dotnet/corefxlab/issues/952 As for scope M#/System C# style, I guess the door is still open for future C# versions.

The great hopac library for F# which is inspired by concurrent ML also supports channels with select. There now also seems to be an experimental channel implementation for C#/.Net which supports this feature: https://github.com/dotnet/corefxlab/tree/master/src/System.T...

Marc Gravell had a good post on Channels/Pipelines too: http://blog.marcgravell.com/2016/09/channelling-my-inner-gee... This is a key part of the .NET roadmap to speed up the basic data pipeline workload of most apps: https://github.com/dotnet/corefxlab/blob/master/docs/roadmap... https://github.com/dotnet/corefxlab/blob/master/src/System.T...

It means that development on Kestrel started before work on making System.Net.Sockets cross-platform was completed. The programming model for libuv and .NET Sockets is different enough (mostly in terms of threading) to make the transition non-trivial. Some recent basic testing show .NET Sockets perform at least as well as libuv. We are strongly considering transitioning Kestrel to Sockets at the same time we migrate from Streams to Pipelines. [1] Pipelines are basically push based Streams that require less total allocations to use. This is because Pipelines allow better memory sharing between producers and consumers. [1] https://github.com/dotnet/corefxlab/tree/master/src/System.I... Disclosure: In case it wasn't already obvious, I work for Microsoft on Kestrel.