So, how much of those gains comes from using the equivalent of malloc/free (FTA: “The most dangerous ArrayPool mistake is forgetting...
So, how much of those gains comes from using the equivalent of malloc/free (FTA: “The most dangerous ArrayPool mistake is forgetting to return arrays. Unlike regular arrays that get garbage collected automatically, pooled arrays must be explicitly returned” ), and how much from having pools of a memory blocks of various sizes? If the former is a significant part, wouldn’t it be useful to just add that to .NET? One would need runtime guards to prevent use after free, but I think at least the “alloc temp buffer for use by function” case isn’t a nightmare to implement (for those working on the .NET runtime)
Posted by Someone on Jan 16, 2026, 1:42 PM
Tags
Related issues
- That isn't really relevant for the tool starting the container.
- Why is there no link to the source?
- Something I wonder about in this domain is if this is the fault of the language.
- Namespace pollution is an annoying problem in Rust.
- Currently, no language ports of Timefold Solver are planned.
- I agree with you, almost all .NET code I write is within the .NET framework, yet when I look at C# repos, it's disheartening to see so ma...
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
hackernews (Software)
That isn't really relevant for the tool starting the container.
NewWhy is there no link to the source?
Something I wonder about in this domain is if this is the fault of the language.
Namespace pollution is an annoying problem in Rust.
Currently, no language ports of Timefold Solver are planned.
I agree with you, almost all .NET code I write is within the .NET framework, yet when I look at C# repos, it's disheartening to see so ma...
Why is there no simple workaround for this?
I have been using https://github.com/jacktasia/dumb-jump to quickly jump to definitions.
So, how much of those gains comes from using the equivalent of malloc/free (FTA: “The most dangerous ArrayPool mistake is forgetting...
So, how much of those gains comes from using the equivalent of malloc/free (FTA: “The most dangerous ArrayPool mistake is forgetting to return arrays. Unlike regular arrays that get garbage collected automatically, pooled arrays must be explicitly returned” ), and how much from having pools of a memory blocks of various sizes? If the former is a significant part, wouldn’t it be useful to just add that to .NET? One would need runtime guards to prevent use after free, but I think at least the “alloc temp buffer for use by function” case isn’t a nightmare to implement (for those working on the .NET runtime)
Comments (0)
No comments yet. Start the discussion.