cell-gc icon indicating copy to clipboard operation
cell-gc copied to clipboard

A very small GC in Rust, with a safe API

Results 23 cell-gc issues
Sort by recently updated
recently updated
newest added

Doesn't seem to actually be a win yet, but it adds nice infrastructure and should be a win with a little bit more work. A few things we can do:...

why not. ---- (checklist by @jorendorff) Things we already sort of do, but sloppily: * [ ] check we correctly parse identifiers * [ ] check behavior of `eqv?` and...

I want a more organized hierarchy of what the layers of a page are, * so it's clear where unsafety resides; and * to support size-classing so I can add...

This might be a useful hack, at least in the short term. For example, in Scheme, `(write-bytevector vec port)` needs to call `writer.write(buf)` on some buffer. But it's unsafe to...

All (mutable) data stored in GC heap pages should be stored inside some kind of cell. I want to do this for a few reasons: * It's almost certainly UB...

Specialization isn't stable in Rust yet, but we can specialize the old-fashioned way: use the mighty `if`. One of the `IntoHeap` traits should have a static method `is_trivial()` which, if...

When I added bytevector support to Scheme, I noticed that to copy a slice of a bytevector I have to copy all the elements out into a new `Vec`, then...

We should have tests for error cases. This is possible now using `with-exception-handler`.

This function exists but currently doesn't work. * [ ] make the parser capable of stopping after one datum is parsed * [ ] make the parser capable of using...

In R7RS users can do this using something called `parameterize`. It would also be ok to provide extension functions that do it. It's all a bit of a chore because...