Go Language Memory Management and Garbage Collection: Difference between revisions
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
The Go compiler decides where a variable is allocated: on the [[#Stack|stack]] or on the [[#Heap|heap]], and it will be garbage-collected correctly. | The Go compiler decides where a variable is allocated: on the [[#Stack|stack]] or on the [[#Heap|heap]], and it will be garbage-collected correctly. | ||
GC can be invoked programmatically: | |||
<syntaxhighlight lang='go'> | |||
runtime.GC() | |||
</syntaxhighlight> | |||
Revision as of 22:21, 2 January 2024
External
Internal
TODO
To deplete, merge and delete this: Go Concepts - Memory Model
Overview
Stack
Heap
Variable Deallocation
Aslo see:
Garbage Collection
Garbage collector is a subsystem of the interpreter that handles de-allocation of memory that is not needed by the program anymore. Garbage collectors can naturally assist interpreted languages, because there is an interpreter. Go is a compiled language, but is different in this respect: it does have garbage collection built into it, even if it does not come with an interpreter.
The Go compiler decides where a variable is allocated: on the stack or on the heap, and it will be garbage-collected correctly.
GC can be invoked programmatically:
runtime.GC()