Problema
The singleton pattern makes sure a class has exactly one instance that everyone shares, a common choice for application settings.
Simulate one shared configuration that starts empty. Process the operations in order:
set <key> <value>: store the value for the key (replacing any old value).get <key>: read the key's current value, ormissingif it was never set.
Because every caller uses the same instance, a value set by one operation is visible to every later get.
Implement shared_configuration(operations).
Input
operations: Strings in the two forms above. Keys and values contain no spaces.
Output
Return the results of the get operations, in order.
Restrições
1 ≤ number of operations ≤ 10,000
Keys and values have 1 to 20 characters
Exemplos
Entrada:
operations = ["set theme dark", "get theme", "get language"]
Saída esperada:
expected = ["dark", "missing"]
Entrada:
std::vector<std::string> operations = {"set theme dark", "get theme", "get language"};
Saída esperada:
std::vector<std::string> expected = {"dark", "missing"};
Entrada:
string[] operations = new string[] {"set theme dark", "get theme", "get language"};
Saída esperada:
string[] expected = new string[] {"dark", "missing"};
Explicação
theme was set to dark; language was never set, so it is missing: ["dark", "missing"].
Entrada:
operations = ["set lang en", "set lang vi", "get lang"]
Saída esperada:
expected = ["vi"]
Entrada:
std::vector<std::string> operations = {"set lang en", "set lang vi", "get lang"};
Saída esperada:
std::vector<std::string> expected = {"vi"};
Entrada:
string[] operations = new string[] {"set lang en", "set lang vi", "get lang"};
Saída esperada:
string[] expected = new string[] {"vi"};
Explicação
The second set replaces the first value in the same shared instance: ["vi"].
Como abordar
Tente sozinho primeiro e depois abra uma dica de cada vez.
Dica 1
All operations read and write the same single object.
Dica 2
A dictionary from key to value is enough to hold the settings.
Dica 3
A key that was never set must return the text missing.
Complexidade esperada
O(number of operations) time, O(number of keys) extra space
Referências
Este desafio foi adaptado para o CodeUtility. Siga o enunciado e as restrições acima.