Comment by KerrAvon 3 months ago Swift, by design, does not have GC. 5 comments KerrAvon Reply pjmlp 3 months ago Chapter 5,https://gchandbook.org/contents.htmlIt would help if all naysayers had their CS skills up to date. pebal 3 months ago RC is a GC method and the least efficient one. winrid 3 months ago It's the most predictable and has much less overhead than a moving collector. pjmlp 3 months ago Only when we forget about the impact of cycle collections, or domino effects stoping the world when there is a cascade of counters reaching zero.The optimisatios needed to improve such scenarions, are akin to a poor man's tracing GC implementation. 1 reply →
pjmlp 3 months ago Chapter 5,https://gchandbook.org/contents.htmlIt would help if all naysayers had their CS skills up to date.
pebal 3 months ago RC is a GC method and the least efficient one. winrid 3 months ago It's the most predictable and has much less overhead than a moving collector. pjmlp 3 months ago Only when we forget about the impact of cycle collections, or domino effects stoping the world when there is a cascade of counters reaching zero.The optimisatios needed to improve such scenarions, are akin to a poor man's tracing GC implementation. 1 reply →
winrid 3 months ago It's the most predictable and has much less overhead than a moving collector. pjmlp 3 months ago Only when we forget about the impact of cycle collections, or domino effects stoping the world when there is a cascade of counters reaching zero.The optimisatios needed to improve such scenarions, are akin to a poor man's tracing GC implementation. 1 reply →
pjmlp 3 months ago Only when we forget about the impact of cycle collections, or domino effects stoping the world when there is a cascade of counters reaching zero.The optimisatios needed to improve such scenarions, are akin to a poor man's tracing GC implementation. 1 reply →
Chapter 5,
https://gchandbook.org/contents.html
It would help if all naysayers had their CS skills up to date.
RC is a GC method and the least efficient one.
It's the most predictable and has much less overhead than a moving collector.
Only when we forget about the impact of cycle collections, or domino effects stoping the world when there is a cascade of counters reaching zero.
The optimisatios needed to improve such scenarions, are akin to a poor man's tracing GC implementation.
1 reply →