f-lawless (@izflawless) header
f-lawless (@izflawless) profile picture

Fear not the machine, nor view it abstract, for yours is the hand that directs every act

Joined October 2026
Photo by f-lawless (@izflawless)Photo by f-lawless (@izflawless)Photo by f-lawless (@izflawless)Photo by f-lawless (@izflawless)Photo by f-lawless (@izflawless)Photo by f-lawless (@izflawless)Photo by f-lawless (@izflawless)
are you guys using trailing return types in c++ or nah?
1
3
58
with some macros and custom type definitions we can make it look look like rust's syntax lol
49
worthy of getting added to your Linux ricing or nah?
1
1
4
345
In the back-end, its just nbfc-linux whirr is only a TUI for more intuition and interaction
16
Why can't I just use std::vector of C++ as an arena allocator and call it a day? I'd never tried it, so I built one and benchmarked it against naive new/delete. Here's what perf says
1
3
139
This is also the best case for an arena: allocate lots, free all at once. malloc is doing far more general work (any size, any order, thread safety). Great for parsers, per-frame game data, and request-scoped memory. Not a malloc replacement.
1
2
Yes, I know the standard library already ships this idea: std::pmr::monotonic_buffer_resource (C++17, <memory_resource>). Same bump-pointer approach, and it plugs into pmr::vector and pmr::string. I wanted to build the bare version first to see where the time goes.
1