diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2018-01-03 00:31:10 -0800 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2018-01-03 00:44:09 -0800 |
commit | acce384bcc88d5b300b913c14b9872081a182155 (patch) | |
tree | a21c33d342c44382b08e37a212a2e79416baca45 /edit | |
parent | c8eb6c1a64d76dc9a1005571c4eb71ddc6d8f2a9 (diff) | |
download | mu-acce384bcc88d5b300b913c14b9872081a182155.tar.gz |
4179 - experiment: rip out memory reclamation
I have a plan for a way to avoid use-after-free errors without all the overheads of maintaining refcounts. Has the nice side-effect of requiring manual memory management. The Mu way is to leak memory by default and build tools to help decide when and where to expend effort plugging memory leaks. Arguably programs should be distributed with summaries of their resource use characteristics. Eliminating refcount maintenance reduces time to run tests by 30% for `mu edit`: this commit parent mu test: 3.9s 4.5s mu test edit: 2:38 3:48 Open questions: - making reclamation easier; some sort of support for destructors - reclaiming local scopes (which are allocated on the heap) - should we support automatically reclaiming allocations inside them?
Diffstat (limited to 'edit')
0 files changed, 0 insertions, 0 deletions