Hmmm. Find some useful information here.
On Wednesday, 9 August 2017 at 17:38:15 UTC, Swoorup Joshi wrote:
Is garbage collection even useful besides managing memory?
GC has the unique advantage of being a global owner, hence
avoiding to encode ownership into types for memory (when you can
use it).
On Wednesday, 9 August 2017 at 17:38:15 UTC, Swoorup Joshi wrote:
On Wednesday, 9 August 2017 at 15:47:17 UTC, Guillaume Piolat
wrote:
On Wednesday, 9 August 2017 at 13:46:29 UTC, MGW wrote:
Memory allocation and deallocation when an application is
being completed in GC operates in FIFO
On Wednesday, 9 August 2017 at 17:38:15 UTC, Swoorup Joshi wrote:
On Wednesday, 9 August 2017 at 15:47:17 UTC, Guillaume Piolat
wrote:
On Wednesday, 9 August 2017 at 13:46:29 UTC, MGW wrote:
Memory allocation and deallocation when an application is
being completed in GC operates in FIFO
On Wednesday, 9 August 2017 at 17:38:15 UTC, Swoorup Joshi wrote:
Is garbage collection even useful besides managing memory?
Managing memory is GC's raison d'être.
On Wednesday, 9 August 2017 at 15:47:17 UTC, Guillaume Piolat
wrote:
On Wednesday, 9 August 2017 at 13:46:29 UTC, MGW wrote:
Memory allocation and deallocation when an application is
being completed in GC operates in FIFO sequence.
Is there a possibility to shift GC memory deallocation to LIFO
On Wednesday, 9 August 2017 at 13:46:29 UTC, MGW wrote:
Memory allocation and deallocation when an application is being
completed in GC operates in FIFO sequence.
Is there a possibility to shift GC memory deallocation to LIFO
mode?
It`s connected with the fact that GUI library (Qt) creates
On Wednesday, 9 August 2017 at 13:46:29 UTC, MGW wrote:
Memory allocation and deallocation when an application is being
completed in GC operates in FIFO sequence.
Not really, it operates in an undefined sequence... just whenever
it gets around to it in scans.
If destruction order is
