Why does containers.Map('KeyType','double') silently return a map with KeyType 'char' ?
15 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
Vijay
am 1 Feb. 2025
Kommentiert: Steven Lord
am 3 Feb. 2025
I would have expected an error if the second argument is strictly required. Giving me a wrong map just pushes the error to runtime when I call it with an 'double' key. No idea what went into this design.
0 Kommentare
Akzeptierte Antwort
Walter Roberson
am 1 Feb. 2025
containers.Map('KeyType','double')
is interpreted as being an instance of calling
M = containers.Map(keySet,valueSet)
You need to provide the 'ValueType' on the same call in order for it to be interpreted as keytype
c = containers.Map('KeyType','double','ValueType','double')
3 Kommentare
Steven Lord
am 3 Feb. 2025
If we allowed users to specify just the KeyType or just the ValueType, the call you wrote would be ambiguous. Do you intend to set just the type and populate the containers.Map object with no data, or did you intend to create a containers.Map object with just one piece of data, where the key just happened to be either 'KeyType' or 'ValueType'?
With the design as implemented, there's no ambiguity. With two inputs you're specifying a key and value pair, even if the key is either 'KeyType' or 'ValueType'. If you want to set one of the types without specifying data you have to explicitly set both types to make it clear you're setting the types.
Note that if you wanted to create an object with two keys, both 'KeyType' and 'ValueType', you could specify a cell array of keys and values.
c = containers.Map({'KeyType', 'ValueType'}, {1, 2})
keys(c)
Weitere Antworten (0)
Siehe auch
Kategorien
Mehr zu Logical finden Sie in Help Center und File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!