This gentleman seems to be talking about a dialect of C# with more functional idioms and parallel-programming friendly features. However, a link describing the actual language itself would have been much more interesting. Briefly looking at the PDF, it doesn't seem to offer much more than rust (apart from .NET interop, which is certainly nothing to sneeze at, if it's your cup of tea), though the mention of a team at Microsoft using it as its primary language and having delivered "millions of lines of code" with it hints at a greater maturity.
The paper is at <a href="http://research.microsoft.com/pubs/170528/msr-tr-2012-79.pdf" rel="nofollow">http://research.microsoft.com/pubs/170528/msr-tr-2012-79.pdf</a> (the redirection fails, but the url is in the query string...)
Interesting goals but....<p>>> 1. Create a single language that incorporates the best of functional and imperative programming. Both offer distinct advantages, and we envisioned marrying the two.<p>Imperative/Functional hybrid are nothing new. C#, Ruby, Python, Javascript, Scala, and Groovy all fit that bill.<p>>> 2. Codify and statically enforce common shared-memory state patterns, such as immutability and isolation, with minimal runtime overhead (i.e., virtually none).<p>"Statically enforcing variable immutability...." Isn't that just a fancy word for "constant"?<p>>> 4. Do all of this while still offering industry-leading code quality and performance, rivaling that of systems-level C programs. Yet still with the safety implied by the above mentioned goals.<p>He wants to allow for "pockets of imperative mutability tied together with functional tissue". That's not a bad thing but it's not exactly a "safe" feature if put in the wrong hands. Lots of people have written function objects with bad imperative code and side effects. Lots of people have fed them to their language's equivalent of the map function. That can cause bugs.
This is a blog article from one of the researchers on a project to bring more immutability to C#, among other things. The paper the article references is well-summarized in a C# context here: <a href="http://www.infoq.com/news/2012/12/Immutable-CSharp" rel="nofollow">http://www.infoq.com/news/2012/12/Immutable-CSharp</a>
another thread, blog ref'g this paper<p><a href="https://news.ycombinator.com/item?id=4871661" rel="nofollow">https://news.ycombinator.com/item?id=4871661</a>