4 ms·
I'm attempting something. https://www.youtube.com/watch?v=Gij9UQy_JEQ https://www.youtube.com/watch?v=Gij9UQy_JEQ https://github.com/pizlonator/llvm-project-d
by pizlonator 3y ago
I'm attempting something.
https://www.youtube.com/watch?v=Gij9UQy_JEQ https://www.youtube.com/watch?v=Gij9UQy_JEQ
https://github.com/pizlonator/llvm-project-deluge/blob/deluge/Manifesto.md https://github.com/pizlonator/llvm-project-deluge/blob/delug...
Right now I'm ~90% through a major rewrite to use GC instead of isoheaps, because then I'll go from rewrite-a-bit (Fil-C previously required malloc calls to be annotated and for some unions to be changed) to rewrite-nothing (malloc will Just Work and so will unions).
I hope there are others also trying various alternatives. It's too soon for most of these things to tell what traction they may or may not get.
- Gibbon1 3y agoTalking about malloc always reminds me of this paper the discusses delaying popping the stack to return temporary objects. https://www.cs.purdue.edu/homes/rompf/papers/xhebraj-ecoop22.pdf https://www.cs.purdue.edu/homes/rompf/papers/xhebraj-ecoop22...
- Animats 3y agoThat seems to be a "fat pointer" scheme, like the one GCC used to have. (Is it still in GCC?)
- pizlonator 3y agoYeah I call them wide ptrs or just capabilities. I haven’t looked at what GCC has in a while because I don’t want to get gpl tainted. :-/