News for hackers. Stuff that matters.
Re:Windows 10 and .NET Native by kevingadd on Saturday October 03, 2015 @04:55PM (#10325334)
This is most likely just an artifact of F# producing unusual IL that's harder to handle. In my experience, it's less 'we only support C#' and more 'compilers other than C#/VB.net produce very strange IL that is hard to handle well' - which is true. Given the small # of users that rely on those weird compilers, it's hard to justify supporting them first, especially if they aren't performance-sensitive.
Re:Windows 10 and .NET Native by MichaelGG on Saturday October 03, 2015 @05:53PM (#10325531)
I emailed the .NET Native team asking them about this. They confirmed that they reverse out IL to higher-level constructs. So they aren't really working at the IL level, they're working on C# represented as IL.

This isn't entirely uncommon. A lot of code that deals with Expression<T> does so very poorly and won't work on many valid trees because they weren't able to get C# to emit certain expressions.