Issue #14762 has been updated by ko1 (Koichi Sasada).


No strong opinion.

They are memo:

I tried to reorder sweeping list by (a) "full page (all slots are living)" and (b)"can sweep page (there are some free-able slots)" and sweep only (b).
No big improvement though :p

I think using ccan we can move the order, so we can try it later?

If we have any trouble to modify them using more complex strategy, we can revert it.


Trivial comments:

* The field name `sweep_pos` seems index for me. Maybe `sweeping_page` or something is fine for me.
* Every time I feel magical for the name `node` (for CCAN list). Should I endure? (page_node or something is clear, but verbose I agree).



----------------------------------------
Misc #14762: [PATCH] gc.c: use ccan/list
https://bugs.ruby-lang.org/issues/14762#change-72027

* Author: normalperson (Eric Wong)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
This seems to improve the readability of gc.c a small amount
and it doesn't have any measurable performance impact.

Code reduction is nice, I might commit it soon:

 gc.c | 81 +++++++++++++++++++++++++++-----------------------------------------
 1 file changed, 32 insertions(+), 49 deletions(-)


---Files--------------------------------
0001-gc.c-use-ccan-list.patch (8.72 KB)


-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>