Confirmed users
328
edits
Managing GC-visible resources: Difference between revisions
→= GC visibility
(Created page with "= Abstract = There is pressure to expose weak references in some way to content, or if not that, at least to use weak references internally for resource management. Weak refe...") |
|||
| Line 27: | Line 27: | ||
The model has a set of references to its views. The views also have back-references to the model, but that is not relevant here. (It is true that you might want the model to be discarded when all views of it are dead, but that is not the problem explored here.) | The model has a set of references to its views. The views also have back-references to the model, but that is not relevant here. (It is true that you might want the model to be discarded when all views of it are dead, but that is not the problem explored here.) | ||
==== GC visibility === | ==== GC visibility ==== | ||
If the invisible view has visible side effects, then it is detectable when the view is collected. It might update shared state or emit log messages, for example. | If the invisible view has visible side effects, then it is detectable when the view is collected. It might update shared state or emit log messages, for example. | ||