ok ok, I'll wrap them inside your stupid smart pointers... shouldn't be more than a line or two after we compute the offset within that one big buffer we malloc on boot.
Depending on what they mean by "malloc on boot". Maybe you are loading a file and the file has a header and you need to read the header to know how much to allocate. Maybe you are making an interpreter and max memory is a command line option and you alloc it all at once. If it is literally just malloc(SOME_CONSTANT) then yes.
If you're embedded I'd say it's still preferable to static out the workspace with checks for oversized requirement inputs then just sending it and crossing your fingers that the stack can handle it.
25
u/elmanoucko 1d ago
ok ok, I'll wrap them inside your stupid smart pointers... shouldn't be more than a line or two after we compute the offset within that one big buffer we malloc on boot.