Re:Allocation is cheap in .NET until it is not
by mrgriffin on Thursday January 25, 2018 @02:49AM
(#16229439)
> Cpython has non-moving GC so this is not an issue.
I believe the GP was referring to PyPy.
From https://morepypy.blogspot.co.uk/2009/10/gc-improvements.html
> The hash field is not necessarily there; it is only present in classes whose hash is ever taken in the RPython program (which includes being keys in a dictionary). It is an "identity hash": it works like object.__hash__() in Python, but it cannot just be the address of the object in case of a GC that moves objects around.
As for having tight coupling between moving GC and hashmap implementation there is another reason why you want to do that: weak pointers and hashmaps that are either weak keyed or weak valued which both are things that are useful for the VM implementation itself (symbol tables, method dispatch caches, identity maps for FFI...).