Heap Approve Countersign with airSlate SignNow

Heap copy countersignature

hello everybody i'm nick in this video i'm going to try to clear up one of the most common misconceptions when it comes down to memory location.net and that is reference types are always allocated on the heap and value types are always allocated on the stack this is false don't say that never say that it's not true i've heard it wrong so many times on interviews stack overflow posts blogs i hear it wrong all the time it's not true only half of it is reference types always get allocated on the heap that's true value types get allocated both on the heap and the stack depending on where they were created and that's what we're going to observe here i'm going to show you exactly what is a stack frame how value types are located how you can inspect them in memory how you can inspect the heap and what's allocated there and how to detect when things are located where you don't expect them to be allocated we're gonna see a lot of things in this video and hopefully at the end of it you should not have any doubt on where your type will be allocated when you're writing your code if you like a ton of content and you want to see more make sure you subscribe to the certification bell to get alerted when i upload a new video so we have two main different type of types in c sharp and that is the value type and the reference type value types can be all this and reference types are basically all the others that don't fall into any of those i'm going to focus on primitives in this video instructs but things like enums or things that implement struct also fall under the same value type category now let's quickly show you something i'm going to create a number and i'm going to just give a random value and i'm going to put a breakpoint here and debug it and the reason why i'm doing that is to show you the memory because writer has a tool here that allows me to load all the heap memory and then scan through that see what's allocated where an integer which is a value type inside a method which is basically a stack frame will cause zero location there's no difference in the allocation nothing was allocated on the heap this value is still being allocated somewhere but that is the stack and that's fine because the moment you're outside of that stack frame the memory in that stack frame just instantly disappears and you don't have to worry about any garbage collection coming in slowing your application down needing to scan for dangling properties and then cleaning them up and you can actually see exactly where this thing is being allocated by using a pointer so i can simply use an unsafe block here and get a pointer to that thing so...