5 ms·
Let’s assume then that there is no GC for parts of the code. It’ll be constantly regenerated
by szundi 3y ago
Let’s assume then that there is no GC for parts of the code. It’ll be constantly regenerated
- xboxnolifes 3y ago> It’ll be constantly regenerated What do you mean by this?
- vrighter 3y agoprobably a misunderstanding of what the GC is and does. The GC works on data, not code.
- staunton 3y agoI think the generous meaning would be an experience like Rust (handles memory allocations/deallocations, doesn't mess up unless you really mess up) except that it doesn't complain all the time when you're doing "ok things" and maybe even makes it impossible in practice to mess up. It could even dynamically decide between using a GC for a given program or not, depending on what makes more sense (thus "constantly generating it").