@alexcoder04@programming.dev to Programmer Humor@programming.devEnglish • 2 years agoData structures…programming.devimagemessage-square13fedilinkarrow-up1106arrow-down111
arrow-up195arrow-down1imageData structures…programming.dev@alexcoder04@programming.dev to Programmer Humor@programming.devEnglish • 2 years agomessage-square13fedilink
minus-square@bronzing@lemmy.fmhy.mllinkfedilinkEnglish6•2 years agoCan someone explain the joke? I know what stacks are but I don’t get it…
minus-square@Gentoo1337@sh.itjust.workslinkfedilinkEnglish4•edit-22 years agoIt’s the last element, so it has to wait for all the other elements on top of it to be popped in order to be accessed I think op meant last as in the element on the bottom
minus-square@bronzing@lemmy.fmhy.mllinkfedilinkEnglish2•2 years agoOh ok I guess that makes sense. Was it that obvious? 😅
minus-square@alexcoder04@programming.devOPlinkfedilinkEnglish2•2 years agoYea, I meant the last element as in the one at the bottom, but now I see that it‘s a little confusing…
minus-square@Gentoo1337@sh.itjust.workslinkfedilinkEnglish1•2 years agoYea I also thought the last one was the bottom one but then I remembered it was lifo
minus-square@wicked@programming.devlinkfedilinkEnglish1•2 years agoMaybe it’s something about not knowing if the last element is the top of the stack or the bottom of the stack?
minus-square@DaleGribble88@programming.devlinkfedilinkEnglish1•2 years agoSplit the difference, it is the only element in a deque.
minus-square@fullcircle@vlemmy.netlinkfedilinkEnglish1•2 years agoHe looks like he’s guarding something? A sentinel value in an array-based stack implementation in C or something? I don’t know, I’m a bit confused too.
Can someone explain the joke? I know what stacks are but I don’t get it…
It’s the last element, so it has to wait for all the other elements on top of it to be popped in order to be accessed
I think op meant last as in the element on the bottom
Oh ok I guess that makes sense. Was it that obvious? 😅
Yea, I meant the last element as in the one at the bottom, but now I see that it‘s a little confusing…
Yea I also thought the last one was the bottom one but then I remembered it was lifo
Maybe it’s something about not knowing if the last element is the top of the stack or the bottom of the stack?
Split the difference, it is the only element in a deque.
He looks like he’s guarding something? A sentinel value in an array-based stack implementation in C or something? I don’t know, I’m a bit confused too.