Stephen Kell
Stephen Kell
It'd be nice to be able to introspect on memory that is allocated by/for Rust code. Currently I don't have a clear enough handle on `rustc` or `cargo` to know...
Conceptually, very little is missing for us to introspect on C++. But one unfortunate thing is that `dumpallocs.ml` does not work on C++ source, so we will need a C++ified...
In `examples/` for some time now I've had a part-done demo allocator that understands memory-mapped ELF files, as an example of a memory-mappable file format. This has a few interesting...
A useful primitive for a lot of tool and diagnostic applications would be "stable allocation identities": instead of a trace or dump that has inscrutable `0xdeadbeef`-esque numbers that change each...
The biggest usability hump with liballocs is identifying allocation functions. I think it's possible to automate this. This meta-issue collects ingredients for doing so. The main idea is a bootstrapping...
Reading #53 and others I'm reminded that we lack a good solution for writes to address-taken union members. In GC terms these are writes that need to be "barriered". There...
Now that there is a Rust-flavoured thing called `liballoc` I wonder whether it is necessary to change the name of liballocs.