Ah, got it—let me clarify a bit.

Right now, I’m working with arrays and slicing them into smaller segments for indexing. Technically, I could rely on bit manipulation to generate much of this, but I’ve chosen to lean into Rust’s type system for that extra layer of expressive control.

In Rust, a slice is essentially a fat pointer: it includes both a memory address and a length. Because the slice type encapsulates both, I don’t need to manually track sizes or offsets. Plus, in debug builds, Rust automatically panics if I try to access an out-of-bounds index, which helps catch issues early. And I can use methods like get or get_mut for safe, optional access—either retrieving a value or returning None.

Ultimately, Rust’s type system saves me from fiddling with raw bit arithmetic and length bookkeeping. It handles validation elegantly, letting me focus on logic instead of low-level guards.

PS: Although it isn’t finished just yet, I’m linking this Node up with a Buf and Slab struct currently. If i remember when I’ve completed the design and I’m happy to freely distribute the code, I’ll make a paste bin and post it here for you. Always happy to help if I can :)

Here is an update. I focused on the Node which is the smallest element of the buffer, it is what contains any meta data and the data payload. The code is heavily reduced but what is shared is pretty much verbatim maybe some minor edits

Update on the Node for my allocator

Yes a Global Allocator to be used with the GlobalAlloc trait

Do you often attempt to but fail to deduct things, you don’t have the skills to perform, or is this a first?

No

I have came accress WGPU. But my goal is to write as close to the OS and other API’s as possible. So i will probably go with Vulkan natively but thanks for the idea!!

I have considered it in the past but JSON feels like the standard. But TOML could be an option. I might try to see which I like better

Your not being rude. You are just wrong, I watched it twice once before you posted when the video was about 6 minutes old, and again when you posted it. I just confirmed that it isn’t a new C.

I saw this the other day. After clicking your link i left a comment but essentially Rust is Rust, it’s more that C/C++ is at the end of its life. But i get the title aiming to mean Rust is taking over C’s role, Rust is a completely differnt beast

I’ve been meaning to try Gleam, I hear really good things about it. Maybe I can make a Gleam-like scripting language for my game-engine.