We use cookies to ensure you have the best browsing experience on our website. Please read our cookie policy for more information about how we use cookies.
Right, but normally the challenges are structured so that the coder's core job is the same as the skill they're trying to teach.
For this problem, that would mean giving the coder some pre-defined stack object/class to work with, so they're mainly thinking in terms of stack operations. This task requires you to implement the stack and define one, which takes away from the core challenge of translating queue operations to stack ones.
Furthermore, by not giving you the stack object, it makes the automated checker not have a way to check that you actually made use of a stack.
Cookie support is required to access HackerRank
Seems like cookies are disabled on this browser, please enable them to open this website
Queues: A Tale of Two Stacks
You are viewing a single comment's thread. Return to all comments →
Right, but normally the challenges are structured so that the coder's core job is the same as the skill they're trying to teach.
For this problem, that would mean giving the coder some pre-defined stack object/class to work with, so they're mainly thinking in terms of stack operations. This task requires you to implement the stack and define one, which takes away from the core challenge of translating queue operations to stack ones.
Furthermore, by not giving you the stack object, it makes the automated checker not have a way to check that you actually made use of a stack.