The TL;DR; version, basically async/await, the UWP AOT compiler, improved handling of value types, spans (aka slices), improved GC (TryStartNoGCRegion()) have their roots in System C# used in Midori.
Also there are some influences of Singularity, namely Bartok and MDIL, on the WP 8.x AOT compiler, but that is not longer relevant.
Ah, so you meant the standard innovations that came out of Midori. I thought you were talking about some new abstraction I hadn't heard of called "outcomes". ¯\_(ツ)_/¯
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 (TryStartNoGCRegion()) have their roots in System C# used in Midori.
Also there are some influences of Singularity, namely Bartok and MDIL, on the WP 8.x AOT compiler, but that is not longer relevant.