Problema
In C++, RAII ties a resource to an object's lifetime: the resource is released automatically when the object goes out of scope. Objects in the same scope are destroyed in reverse order of creation.
Process the events in order:
{: enter a new inner scope.}: leave the current scope; every resource acquired in it is released, newest first.acquire <name>: create a resource in the current scope.
When the events run out, the remaining open scopes end from the innermost to the outermost (the program's outer scope included), releasing their resources the same way.
Implement raii_release_order(events).
Input
events: The events. Braces are balanced or left open, never closed without being opened.
Output
Return the resource names in the order they are released.
Restrições
0 ≤ number of events ≤ 100,000
Names have 1 to 20 characters without spaces
Exemplos
Entrada:
events = ["acquire db", "{", "acquire file", "acquire lock", "}", "acquire log"]
Saída esperada:
expected = ["lock", "file", "log", "db"]
Entrada:
std::vector<std::string> events = {"acquire db", "{", "acquire file", "acquire lock", "}", "acquire log"};
Saída esperada:
std::vector<std::string> expected = {"lock", "file", "log", "db"};
Entrada:
string[] events = new string[] {"acquire db", "{", "acquire file", "acquire lock", "}", "acquire log"};
Saída esperada:
string[] expected = new string[] {"lock", "file", "log", "db"};
Explicação
Leaving the inner scope releases lock then file (newest first). At the end the outer scope releases log then db: ["lock", "file", "log", "db"].
Entrada:
events = ["{", "acquire a", "{", "acquire b"]
Saída esperada:
expected = ["b", "a"]
Entrada:
std::vector<std::string> events = {"{", "acquire a", "{", "acquire b"};
Saída esperada:
std::vector<std::string> expected = {"b", "a"};
Entrada:
string[] events = new string[] {"{", "acquire a", "{", "acquire b"};
Saída esperada:
string[] expected = new string[] {"b", "a"};
Explicação
Two scopes are still open at the end: the innermost releases b, then the next releases a: ["b", "a"].
Como abordar
Tente sozinho primeiro e depois abra uma dica de cada vez.
Dica 1
Keep a stack of scopes, each holding its resources in order.
Dica 2
Closing a scope releases its resources from newest to oldest.
Dica 3
At the end, close every scope that is still open, innermost first.
Complexidade esperada
O(number of events) time, O(number of events) extra space
Referências
Este desafio foi adaptado para o CodeUtility. Siga o enunciado e as restrições acima.