I don't consider cyclic gc to be an experiment anymore. It's proved to be very solid code, and it hasn't become orphaned either <wink>. What say ye to nuking the #ifdefs conditionalizing it in the core for 2.3? They're irritating, the code base without cyclic gc is never tested, the touchy trashcan mechanism works in a radically different way when cyclic gc isn't compiled in, and if cyclic gc is compiled in it's easy to turn it off at will (gc.disable()). It does cost memory for the gc header on containers, but since we never test without it the ability to compile it out isn't much of "a feature". +1 from me <ahem>.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4