#8255: GC Less Operation -------------------------------------+------------------------------------- Reporter: sirinath | Owner: Type: feature request | Status: closed Priority: lowest | Milestone: _|_ Component: Compiler | Version: 7.7 Resolution: invalid | Keywords: Operating System: Unknown/Multiple | Architecture: Unknown/Multiple Type of failure: Runtime | Difficulty: Project (more performance bug | than a week) Test Case: | Blocked By: Blocking: | Related Tickets: -------------------------------------+------------------------------------- Comment (by sirinath): Thought memory is not manually managed does not mean that memory can only be managed in a language like Haskell though a GC. GC can be fall back. At the language level there may be no distinction between value and reference under the hood they are either on the stack or heap. The heap has to be managed. Also allocation / de allocation can be in bocks in Haskell opposed to object at a time based on memory allocation in execution locality. Allocation and de allocation can be executing thread by inseting these into the flow of the program at the compiled code level. ARC in Objective c context cannot be implemented as it is in Haskell. Romacing with the GC is more of a philosophical decision with current state of compiler technology. Some years back gc would have been the only option for languages without explicit memory management. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/8255#comment:6 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler