Traditionally alloca is horrible and a source of non-reportable errors. Does the Rust one do less horribly?
If you want a "managed stack", there go your performance benefits over using an allocator. :-)
-
-
whut? I want reliable stack overflow checking, that's it
-
Overflow checking that traps/crashes is easy. Making () operator something that can fail & report failure is not.
-
I plan to reserve space for unwinder state and unwind from the prologue, if panicking is enabled
-
if unwinding on panicking is enabled* (if not then any panic at all will crash the process anyway)
-
Doesn't sound like a plan for producing robust sw with good ux...
-
do you understand how error handling generally works in Rust? if not I suggest reading up on it
-
what I'm doing here isn't specific to alloca, it rather extends existing mechanisms to cover allocation
-
Supporting allocating more than a page on the stack seems like it might be excessive.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.