AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Stack vs heap in golang11/8/2023 The Heap is similar except that its purpose is to hold information (not keep track of execution most of the time) so anything in our Heap can be accessed at any time. When we're done with the top box (the method is done executing) we throw it away and proceed to use the stuff in the previous box on the top of the stack. We can only use what's in the top box on the stack. We keep track of what's going on in our application by stacking another box on top every time we call a method (called a Frame). Think of the Stack as a series of boxes stacked one on top of the next. The Heap is more or less responsible for keeping track of our objects (our data, well. The Stack is more or less responsible for keeping track of what's executing in our code (or what's been "called"). They reside in the operating memory on our machine and contain the pieces of information we need to make it all happen. Both the stack and heap help us run our code. If you haven't already met, let me introduce you to the Stack and the Heap. NET framework stores items in memory as your code executes. In this article, I'll cover the basics of the Stack and Heap, types of variables, and why some variables work as they do. Also, having a basic understanding of how memory management works will help explain the behavior of the variables we work with in every program we write. NET framework we don't have to actively worry about memory management and garbage collection (GC), we still have to keep memory management and GC in mind in order to optimize the performance of our applications.
0 Comments
Read More
Leave a Reply. |