5 ms·
Nim does much the same. It prefers the stack, wraps dynamic heap types in value-semantic unique pointers by default, and avoids implicit copies wherever it can.
by netbioserror 4mo ago
Nim does much the same. It prefers the stack, wraps dynamic heap types in value-semantic unique pointers by default, and avoids implicit copies wherever it can. I could see compiled languages trending in the stack-managed direction long term.
- zozbot234 4mo agoIt's more like a seamless generalization of the "stack-managed" pattern since async contexts also usually manage resources but don't reside on a stack.