8000 gh-119786: Move garbage collection doc from devguide to InternalDocs by iritkatriel · Pull Request #125282 · python/cpython · GitHub
[go: up one dir, main page]

Skip to content

gh-119786: Move garbage collection doc from devguide to InternalDocs #125282

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Oct 11, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fixup
  • Loading branch information
iritkatriel committed Oct 10, 2024
commit 8153c0f87e2dd619cfe6113d118b11f4e948dbb3
4 changes: 2 additions & 2 deletions InternalDocs/garbage_collector.md
Original file line number Diff line number Diff line change
Expand Up @@ -105,8 +105,8 @@ information associated to the GC is needed the previous fields can be accessed b
simple type cast from the original object: `((PyGC_Head *)(the_object)-1)`.

As is explained later in the
[Optimization: reusing fields to save memory](#Optimization-reusing-fields-to-save-memory] section,
these two extra fields are normally used to keep doubly linked lists of all the
[Optimization: reusing fields to save memory](#optimization-reusing-fields-to-save-memory)
section, these two extra fields are normally used to keep doubly linked lists of all the
objects tracked by the garbage collector (these lists are the GC generations, more on
that in the [Optimization: generations](#Optimization-generations) section), but
they are also reused to fulfill other purposes when the full doubly linked list
Expand Down
Loading
0