colang icon indicating copy to clipboard operation
colang copied to clipboard

Memory management (AOT malloc + free versus GC; stack versus heap)

Open dumblob opened this issue 4 years ago • 0 comments

How do you plan to do memory management (stack and heap if applicable)?

Do you want to even use heap?

If so, will you want to do extensive analysis (like Lobster, Passerine, V, and a bit Basil) to avoid garbage collector at all (i.e. insert ahead of time all the needed malloc & free calls) or do you just want to use a garbage collector?

If not, how will your stack memory management look like? Will it be a pure continuation passing style? Or rather something like Forth (and other concatenative languages)? Or some kind of (partially) virtual memory (imagine https://github.com/josephg/jumprope-rs or alike or https://www.codeproject.com/Articles/3479/The-Bip-Buffer-The-Circular-Buffer-with-a-Twist or alike)? Or some hybrid like stack-based allocation in Basil?

dumblob avatar Oct 16 '21 09:10 dumblob