7 Dec
2022
7 Dec
'22
6:08 p.m.
On Wed Dec 7 17:50:04 2022 +0000, Gabriel Ivăncescu wrote:
That's correct, it can't. What the comment says is that the next object might have been removed during unlinking, so we have to obtain it again here, *after* unlinking, since the old iter might be pointing to a freed object. If you have ideas to make it clearer please let me know.
How about something like: /* Releasing unlinked object should not delete any other object, so we can safely obtain the next pointer now */