diff options
| author | Pablo Galindo <Pablogsal@gmail.com> | 2019-11-19 01:36:57 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-11-19 01:36:57 (GMT) |
| commit | b028f589ddf6041d2fab7eb50384588f199864b3 (patch) | |
| tree | 67f4b96581de07cf2bd9727b63f92a4267fa023e /Modules/gcmodule.c | |
| parent | dcf1f83de8678b09df5bd7d04ca5f4ef1cd02aca (diff) | |
| download | cpython-b028f589ddf6041d2fab7eb50384588f199864b3.zip cpython-b028f589ddf6041d2fab7eb50384588f199864b3.tar.gz cpython-b028f589ddf6041d2fab7eb50384588f199864b3.tar.bz2 | |
Minor fixes to the formatting of the notes of Modules/gcmodule.c (GH-17247)
Diffstat (limited to 'Modules/gcmodule.c')
| -rw-r--r-- | Modules/gcmodule.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Modules/gcmodule.c b/Modules/gcmodule.c index b258a0f..cb7a3de 100644 --- a/Modules/gcmodule.c +++ b/Modules/gcmodule.c @@ -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 @@ -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. |