Two more significant bugs have been found when using RyuJIT and .NET 4.6. Code recompilation is not necessary to experience the effects, merely running existing code on RyuJIT (which ships in .NET 4.6 and is enabled by default) will cause severe problems.
Continuing our look at the future of C#, we now take a look at Proposal 119. This would add first class compiler and syntax support for method-level contracts.
In C#, the readonly keyword can only be used at the field level. Under proposal 115, Readonly for Locals and Parameters, this would be extended to cover a many more scenarios.
Though on the “Some Interest” list, the next proposal is very controversial. The basic premise for the Lambda Capture Lists proposal is that it would allow more control over how variables are captured in closures.
Code Aware Libraries are “libraries that provide guidance on correct use through embedded tooling and operates on the user’s code in real time.”
The next proposal in our C# Futures series considers the possibility of offering extension fields. This in turn would allow for extension properties and extension events.
The async/await syntax in C# was well received, but now developers are asking for more. Specifically, they want to be able to return more than one value from their asynchronous function using a “yield return” like syntax. This capability is being referred to as “asynchronous sequences” in a new proposal for C# 7.
A big emphasis for many developers, especially those writing games or working on pure number crunching, is raw performance. One way to get more performance out of C# is to avoid allocating memory without having to copy structs instead. The next proposal shows how C# can expose the CLR managed pointer support to do just that.
Probably the most common error type in .NET is the Null Reference Exception. The root cause of this error is C#’s inability to express the concept of non-nullable references, which in turn makes compiler-enforced null checking it too burdensome. To address this problem, there is a proposal for mandatory and explicitly nullable references.
With C#6 nearing completion, plans are already being laid for C# 7. While nothing is definite yet, they are starting to categorize proposals in terms of “interest and estimated plausibility”. In this series, we’ll be looking at some of the proposals starting with language support for tuples.
The .NET Foundation has announced the release of a new project called LLILC (pronounced "lilac"). The project, initiallycontributed by Microsoft, aims to provide a new LLVM-based native code compiler for .NET Core which will make it possible to run .NET programs "on any platform that CoreCLR can be ported to and that LLVM will target."
A major limitation of the .NET framework is its inability to truly work with the Windows file system. Even seemingly basic operations such as working file paths longer than 260 characters long is beyond the capabilities of System.IO. This is where AlphaFS comes into play.
Like most languages that rely on a mark-and-sweep garbage collector, C# can run into performance problems when allocating memory too often or when making large allocations. Ben Watson, a Senior SDE at Microsoft working on Bing, ran into just that problem with the MemoryStream class.
With C# 6 nearly complete, work has begun on the next version. Like past versions, the first step is to set an overall theme and scope for what is to come. That vision has been shared by Mads Torgersen by publishing the first set of meeting notes for the C# 7 design team.
amarin last week announced version 8.6 of its iOS SDK (Xamarin.iOS), the first non-beta release to include the company's Unified API for iOS and Mac. The Unified API replaces the 32-bit MonoTouch and MonoMac APIs, enabling code re-use across both platforms and adding 64-bit support.