Skip to content

Minor fixes to the formatting of the notes of Modules/gcmodule.c #17247

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 1 commit into from
Nov 19, 2019
Merged
Changes from all commits
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
4 changes: 2 additions & 2 deletions Modules/gcmodule.c
Original file line number Diff line number Diff line change
Expand Up @@ -1088,7 +1088,7 @@ deduce_unreachable(PyGC_Head *base, PyGC_Head *unreachable) {
* NOTE: This used to move the reachable objects into a reachable
* set instead. But most things usually turn out to be reachable,
* so it's more efficient to move the unreachable things. See note
^ [REACHABLE OR UNREACHABLE?} at the file end.
^ [REACHABLE OR UNREACHABLE?] at the file end.
*/
gc_list_init(unreachable);
move_unreachable(base, unreachable); // gc_prev is pointer again
Expand Down Expand Up @@ -2188,7 +2188,7 @@ PyObject_GC_Del(void *op)
/* ------------------------------------------------------------------------
Notes

[REACHABLE OR UNREACHABLE?}
[REACHABLE OR UNREACHABLE?]

It "sounds slick" to move the unreachable objects, until you think about
it - the reason it pays isn't actually obvious.
Expand Down