Thanks for sharing! That's a much more interesting project compared to mine xD. I had the intuition that rust-gc could be implemented in a simpler fashion by not being generic. Glad to see someone actually had it done.
Thanks for writing the book! I've had an amazing experience tinkering with it over the years. I see that the license now includes images. I was unsure of how to have proper attribution and had just a link to a…
Yes, the borrows were only held for roughly a single instruction. But I don't see how you can mutate the Table/HashMap of fields in an object with only Cell tho
haha, glad to know that I'm not the only one
Nice, thanks for sharing. Definitely gonna look into how you do it, I couldn't get as close to clox like you did
Yeah, it's a self-enforced contract that objects of type Gc<T> are only ever touched by the virtual machine, but I get your point.
Yeah true, this breaks all sorts of contracts that we have with Rust xD. But if mark-and-sweep is implemented correctly, then no reference is ever held across the GC. Though, there's gonna be lots of pain debugging when…
Thanks for sharing! That's a much more interesting project compared to mine xD. I had the intuition that rust-gc could be implemented in a simpler fashion by not being generic. Glad to see someone actually had it done.
Thanks for writing the book! I've had an amazing experience tinkering with it over the years. I see that the license now includes images. I was unsure of how to have proper attribution and had just a link to a…
Yes, the borrows were only held for roughly a single instruction. But I don't see how you can mutate the Table/HashMap of fields in an object with only Cell tho
haha, glad to know that I'm not the only one
Nice, thanks for sharing. Definitely gonna look into how you do it, I couldn't get as close to clox like you did
Yeah, it's a self-enforced contract that objects of type Gc<T> are only ever touched by the virtual machine, but I get your point.
Yeah true, this breaks all sorts of contracts that we have with Rust xD. But if mark-and-sweep is implemented correctly, then no reference is ever held across the GC. Though, there's gonna be lots of pain debugging when…