News for hackers. Stuff that matters.
Re:Porting the Unity Engine to .NET CoreCLR by pjmlp on Wednesday April 11, 2018 @04:01PM (#16814933)
> Some of those like span are more of a library or jit features than language things.

Sure, C++ also has got its span and string_view as library.

> There is still a lot to be done to match C++, in the meantime syntax is getting uglier and uglier ...

Actually I find the opposite regarding syntax.

Don't forget C# has roots on the Pascal/Algol family of languages, even if it the syntax is C like.

For example Modula-3 also has the same REF and READONLY, just in caps. :)

Type classes, well kind of nice, not really into them, given interfaces.

Generics specialization is more a matter of improving the compilers (JIT/AOT).

Here .NET Native might be interesting given that it uses the same backend as Visual C++.

As for the rest, I never felt it was that slow and even with the current language semantics, Unity is quite confident that their new AOT compiler is able to take advantage of the HPC# subset (which still is 100% valid C#) to start moving C++ engine parts into C#.

Re:Porting the Unity Engine to .NET CoreCLR by polskibus on Thursday April 12, 2018 @02:59AM (#16818603)
Will regular .NET or .NET core be able to take advantage of HPC#?
Re:Porting the Unity Engine to .NET CoreCLR by pjmlp on Thursday April 12, 2018 @07:48AM (#16819851)
No, it is a special AOT compiler (Burst) that is aware of Unity semantics and the C# subset.

https://www.youtube.com/playlist?list=PLX2vGYjWbI0S8ujCJKYT-...

The talk "C# Sharp to Machine Code" contains the details how it works, while the other ones explain all the Unity engine pieces that are being moved from C++ into HPC#.

.NET or .NET core benefit from this work, by the feedback Unity is giving back to Microsoft, as Miguel explained on his interview at Unity's booth.