News for hackers. Stuff that matters.
Re:Classes vs. Structs in .NET. How not to teach about perfo... by Const-me on Sunday November 05, 2023 @11:55PM (#38159013)
> How is that relevant to the vast majority of the code targeted by LINQ?

The people I responded to were discussing applicability of LINQ. I think very fast sum of List<int> collections doesn’t compensate for suboptimal performance of pretty much everything else.

For 80% of problems that “suboptimal” is still fast enough for the job, but for other 20% it’s important. Using the same C# language it’s often possible to outperform LINQ by a large factor, using loops, SIMD intrinsics, and minimizing GC allocations.

> partially covered by a recent System.Numerics.Tensors package

They don’t generate code in runtime, they treat C# as a slower and safer C. I’m pretty sure the higher-level parts of the runtime allow more advanced stuff, similar to expression templates in Eigen, but better because runtime codegen could account for different ISA extensions, and even different L1/L2 cache sizes.

Re:Classes vs. Structs in .NET. How not to teach about perfo... by neonsunset on Monday November 06, 2023 @03:44AM (#38160130)
I see, my bad, should not have responded to your comments.