I accidentally wrote
std::set<string> keys;
as:
std:set<string> keys;
but weirdly enough, Visual Studio 2013 still compiles.
Why does this happen?
Actually keys
is not only defined, but later used as a set of strings, such as
if(keys.find(keystr)==keys.end()){
keys.insert(keystr);
toret.push_back(tempv);
}
std::set is an associative container that contains a sorted set of unique objects of type Key . Sorting is done using the key comparison function Compare. Search, removal, and insertion operations have logarithmic complexity.
Per the C++ standard, iteration over the elements in an std::set proceeds in sorted order as determined by std::less or by the optional comparison predicate template argument.
Sets are a type of associative container in which each element has to be unique because the value of the element identifies it. The values are stored in a specific sorted order i.e. either ascending or descending.
At block scope, an identifier followed by a single colon introduces a label. Thus, your statement is equivalent to:
set<string> keys;
except that it bears the label std
and can be jumped to by the statement goto std;
.
For some reason, the name set
is known to the compiler---perhaps you did using namespace std;
, or using std::set;
, or something like that, or perhaps you defined your own set
type somewhere.
In the second case, std is a label. It is the same as spelling default incorrectly in a case statement.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With