





















openat2 has RESOLVE_NO_SYMLINKS


RESOLVE_BENEATH also sounds very interesting
open(2) with O_NOFOLLOW and slowly open your way through the entire path 

RESOLVE_BENEATH also sounds very interesting 

open(2) with O_NOFOLLOW and slowly open your way through the entire path 






openat2 has RESOLVE_NO_SYMLINKS 

RESOLVE_BENEATH




openat2 is very new, and tough/slow to emulate outside the kernel correctly

openat2 is very new, and tough/slow to emulate outside the kernel correctly 


openat2 is very new, and tough/slow to emulate outside the kernel correctly 

rg or fd





RESOLVE_IN_ROOT is also useful. It should make implementing stuff like sandboxing so much easier and safer to implement


RESOLVE_IN_ROOT is also useful. It should make implementing stuff like sandboxing so much easier and safer to implement 





























wasmer.io thing? Are we getting a new flatpak kinda thing with builtin virtualization so one binary can be shipped?

wasmer.io thing? Are we getting a new flatpak kinda thing with builtin virtualization so one binary can be shipped? 























































Result type and garbage collection isn't desirable either, but it is a comfy language

Result type and garbage collection isn't desirable either, but it is a comfy language 

Result type and garbage collection isn't desirable either, but it is a comfy language 




remove_vote command, the entire heap of vote options is allocated again without the entry being removed. This allocation was not considering the required alignment for CVoteOptionServer objects and potentially wasting space by aligning with alignof(std::max_align_t). When allocating the entries with the add_vote command, the alignment is already specified correctly.










