DistIL
UnityH4xx
DistIL | UnityH4xx | |
---|---|---|
4 | 1 | |
108 | 35 | |
- | - | |
8.5 | 2.6 | |
8 days ago | about 1 year ago | |
C# | C# | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
DistIL
-
Classes vs. Structs in .NET. How not to teach about performance
How is that relevant to the vast majority of the code targeted by LINQ?
The niche scenario you have outlined is partially covered by a recent System.Numerics.Tensors package update (even though I believe it would have been best if there was a community-maintained package with comparable quality that can be decoupled from .NET release cycle and trade-off support/compat guarantees in favour of more aggressive improvements in the future).
The goal of LINQ itself is to offer optimal codepaths when it can within the constraints of the current design (naturally, you could improve it significantly if not for backwards compatibility with the previous 15 or so years of .NET codebases). The argument that it's not good because it's not the tool to do BLAS is just nonsensical.
There is, however, an IL optimizer that can further vectorize certain common patterns and rewrite LINQ calls into open-coded loops: https://github.com/dubiousconst282/DistIL
-
DistIL: Experimental optimizer and intermediate representation for .NET IL
Repo: https://github.com/dubiousconst282/DistIL
- DistIL: An experimental optimizer and compiler IR for .NET CIL
-
What's the benefit of local functions?
The lifetime problem should not be that complicated, because the class/lambda allocation is contained entirely within the method. There's an open issue on the runtime repo about object stack allocation that would on paper alleviate some of these issues, but it's quite stagnated. In my toy optimizer, I made a buggy pattern matching transform for "concretizing" lambdas invocations using very little code, but implementing something like this in the JIT can be quite challenging, based on my limited experience.
UnityH4xx
What are some alternatives?
NetFabric.Hyperlinq - High performance LINQ implementation with minimal heap allocations. Supports enumerables, async enumerables, arrays and Span<T>.
libplanet - Blockchain in C#/.NET for on-chain, decentralized gaming
mongo-csharp-analyzer - The MongoDB Analyzer is a free tool that helps you understand how your code translates into the MongoDB Query API.
Reflex - Minimal dependency injection framework for Unity
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
IL2C - IL2C - A translator for ECMA-335 CIL/MSIL to C language.
Arch.Extended - Extensions for Arch with some useful features like Systems, Source Generator and Utils.
AStar - A fast 2D path finding library based on the A* algorithm. Works with both grids and graphs. Supports any .NET variant that supports .NETStandard 2.0 or higher. This library has no external dependencies. The library is licensed under the MIT license.
Arch - A high-performance C# based Archetype & Chunks Entity Component System (ECS) with optional multithreading.
Entitas - Entitas is a super fast Entity Component System (ECS) Framework specifically made for C# and Unity