Robin Sommer 0767598771 GH-293: Protect copy() against reference cycles. ... Reference cycles shouldn't occur but there's nothing really preventing people from creating them, so may just as well be safe and deal with them when cloning values. While the code is a bit more cumbersome this way, it could actually be bit faster as well as it no longer caches non-mutable values. (I measured it with the test suite: That's about the same in execution time, maybe tiny little bit faster now; definitly not slower).		2019-06-03 15:20:30 +00:00
..
out	GH-293: Protect copy() against reference cycles.	2019-06-03 15:20:30 +00:00