AStack | The Missing SwiftUI Adaptive and Accessible Stacks Library | iOS library

You're calling DrawerContent like a normal function, not using it as a tag. As a result, DrawerContent will not have life cycle or state, it's just a normal function, return stuff. You need to invoke it by using JSX syntax, then DrawerContent will have life cycle and you can useSelector there.

Starting off, I just want to point out that the use of classes is for data hiding. Making your top, size, and other data members of public scope completely defeats the purpose. Secondly, the nomenclature of classes should start with an uppercase alphabet.

The first error is with your stack::Push(char) method. Note the difference between return astack[--top] and return astack[top--]. The former decreases the value of top by 1, and then returns the value, whereas, the latter returns the value of astack[top] and then decrements top.

This is very crucial as what you really want is to return the value popped, and not the value at the top of the stack after popping.

no, the second structure will not work if you remove the three-screen which are under MyFavoritePost component then u cannot use navigation.navigate() to go to that screen. you can do one thing you can create a stack navigator separate for these three screens and use in MyFavoritePost component. else first structure is perfect.

Your stack class has miscellaneous problems already pointed out in the comments. With those fixed, only a few bugs in the main program remained.

I've used a std::unique_ptr<> in your array instead of a raw pointer and disabled move semantics so it's neither copyable (because of the unique_ptr) nor moveable.

I also added throwing exceptions if you try to access the stack out of bounds.