New week, new Rust! What are you folks up to?
I am thinking about making a better ( actually safe! ) “local” allocator.
I want to exploit that the expected allocation/deallocation pattern is either “temporary” thread-local allocations or longer allocations that don’t outlast the thread.
Currently I just ASSUME this, and it isn’t checked, which isn’t safe, even though I know it will work in practice due to the overall structure of my program.
So I should really take deallocation more seriously than just decrementing a counter. At minimum I should be checking it came from the “current” local chunk of memory, and if it doesn’t I should look locally and globally for where it came from. Well something like that, this is what I am thinking about.
Maybe I can send “unusual” deallocations to some central async(?) process that figures them out. Some “blocks” would be (temporarily) owned by local allocators in which case deallocations to those blocks may be delayed until the ownership returns to the central process Umm..
Has anyone written a serious memory allocator in Rust up to now?
Later…
In the end I realised all I have to do is to check deallocations are in range, which is a very cheap check, as typically it is just two integer compares. Then everything is safe ( although deallocating on a different thread will abort the process ).
1 Like
After 1.5 years of late nights and weekends I finally released The Portsmoor Abysm, my hobby game, built in Rust+Bevy, on Steam. So now comes the part where I need to maintain it.
5 Likes
Nice! It looks like a modern take on Boulder Dash.
1 Like
µTate adaptive music visualizer using Vulkan and slang.
Should get my pipelines and stages going today. Using bon to make the target support fluent.
1 Like
I am beta testing a new tool that will be released soon as open source in rust community
1 Like
Been experimenting with egui for desktop application. pretty fun so far.
Indeed, playing Boulder Dash on my C128D as a kid was my initial inspiration 
1 Like