Persistent data structure: Difference between revisions

Revision as of 20:35, 21 May 2022

Revision as of 19:50, 18 June 2022

Line 185:

==Garbage collection==

Because persistent data structures are often implemented in such a way that successive versions of a data structure share underlying memory<ref>{{Cite web|url=https://kostyukov.net/posts/designing-a-pfds/|title=Vladimir Kostyukov - Posts / Slides|website=kostyukov.net|access-date=2018-11-30}}</ref> ergonomic use of such data structures generally requires some form of [[automatic garbage collection]] system such as [[reference counting]] or [[mark and sweep]].<ref>{{Cite web|url=http://wiki.c2.com/?ImmutableObjectsAndGarbageCollection|title=http://wiki.c2.com/?ImmutableObjectsAndGarbageCollection|website=wiki.c2.com|access-date=2018-11-30}}</ref> In some platforms where persistent data structures are used it is an option to not use garbage collection which, while doing so can lead to [[memory leak]]s, can in some cases have a positive impact on the overall performance of an application.<ref>{{Cite web|url=https://www.infoq.com/news/2017/03/java-epsilon-gc|title=The Last Frontier in Java Performance: Remove the Garbage Collector|website=InfoQ|access-date=2018-11-30}}</ref>

==See also==