Coding Shorts: Making Sense of Stack vs. Heap

This is a different kind of video that I usually make. The topic of how memory is handled in a variety of languages is a key concept every developer should have a handle on. In this quick tutorial, I try and explain how it works. Take a look!
If you like this video, you might like other videos in my Instructional Videos:
• Instructional Videos

[@RobertSagoe]

Your explanation is clear and concise, making the process easy to understand. Thank you for the details and excellent graphical explanation .. really helpful

[@swildermuth]

Glad you enjoyed it!

[@gandodiallo4146]

You are the best Shawn

[@LUNTE1337]

Excellent explanation and visualization!

[@swildermuth]

Glad you liked it!

[@tak8460]

Nice explanation. It helped clarify a few things. Thank you for your efforts!

[@swildermuth]

You are welcome!

[@adsfaedaer]

when the stack pops what happens to a struct - which is a value type - that contains a string. is the string immediately culled (because the struct has been cleaned up) or does it wait around for the GC? - also how many pancakes where consumed after you did this ?

[@swildermuth]

any reference types that the struct is holding on to will be released to the GC but not disappear immediately. The Struct is a value type but it doesn't promote members of the struct to value types, remember the reference types in the struct are just the addresses of the reference types in the heap. Does that make sense?

[@heavypeki]

@@swildermuth Perfectly makes sense. Struct in itself is a value type, but isn't responsible for its own members which could be address pointer.

[@kinsondigital]

Great explanation!! Love it!

[@swildermuth]

So glad!

[@williamliu8985]

Is it able to see if the target is in stack or heap when debugging?

[@swildermuth]

I don't see a way, but of course, you can see the type (and infer it's on the stack) - might want to look at C# boxing too (essentially making a reference to a value type so that it becomes a reference type).

[@williamliu8985]

@@swildermuth Thanks! It would be nice if their locations were clearly indicated in the debugger so that programmers don't have to guess about such a basic but important concept.