/explore
|
You are here 
|
journal.stuffwithstuff.com | ||
| | | | |
danilafe.com
In this post, we implement a garbage collector that frees memory no longer used by the executables our compiler creates. |
|
| | | | | ||
| | | | |
boats.gitlab.io
In the previous post I said that in the second post in the series we'd talk about how rooting works. However, as I sat down to write that post, I realized that it would be a good idea to back up and give an initial overview of how a tracing garbage collector works - and in particular, how the underlying garbage collector in shifgrethor is implemented. In the abstract, we can think of the memory of a Rust program with garbage collection as being divided into three sections: the stack, the "unmanaged" heap... |
|
| | | | | ||
| | | | |
maplant.com
|
|
| | | | | ||
| | | | |
nora.codes
[AI summary] The article explains the concept of 'unsafe' in Rust, clarifying that it allows specific low-level operations while maintaining overall memory safety through the language's type system and safe abstractions. |
|
| | | |||
