1463679 - GCManagedDeletePolicy is a misnomer

Status: RESOLVED INVALID

(Core :: JavaScript: GC, enhancement, P5)

Description

[Jon Coppeard (:jonco)]

We have this delete policy for things that contain GC pointers but have non-GC lifetime (i.e. they can be destroyed outside of a GC) which will ensure GC invariants are maintained by invoking write barriers for GC pointers on destruction.

Note that destruction can also happen part way through initialisation if there is an error.  It's arguable whether we need to do this in that case (it depends on whether any of the partly-initialised state can escape) but sometimes it's better to be safe than sorry.  It doesn't help that cases like these are not always covered by our tests.

Anyway, this is more like a delete policy for non-GC lifetime things than contain GC pointers.  So I'm not sure what this should be called but GCManagedDeletePolicy doesn't seem right.

Comment 1

[Jon Coppeard (:jonco)]

GCManagedDeletePolicy has been removed.