-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Description
The title for section 15.6 is "Creating Reference Cycles and Leaking Memory is Safe". At a glance this could imply that Rust magically cleans up after you somehow, which might be deceptive to new people (even though you explain exactly what you mean in the first paragraph after that title). An alternative might be to just say "Creating Reference Cycles and Leaking Memory is Not Unsafe".
It might also be worth saying that, while Rust doesn't guarantee lack of memory leaks, under most circumstances the only way it will happen is if you create cycles through refcounted pointer types. Just saying "preventing memory leaks is not one of Rust's guarantees" leaves open the possibility that safe code which does not create refcount cycles still could leak memory, which as far as I know should never happen.