containers.Map.keys — Return a row cell array of a map's keys in RunMat key order.
Return a row cell array of a map's keys in RunMat key order. The output preserves the native class of numeric keys, including uint64 keys beyond binary64 exactness. The result is host-resident.
Syntax
K = containers.Map.keys(M)Inputs
M- Type
Any- Required
- Yes
- Default
- —
- Description
- containers.Map handle object.
Returns
K- Type
Any- Description
- Row cell array containing map keys.
Errors
RunMat:containers.Map:InvalidArgument- When
- Map constructor/method inputs, option grammar, or key/value payloads are invalid.
- Message
containers.Map: invalid argument
RunMat:containers.Map:MissingKey- When
- Lookup/removal targets a key that is not present in the map.
- Message
containers.Map: The specified key is not present in this container.
RunMat:containers.Map:Internal- When
- Map registry/storage operations fail unexpectedly.
- Message
containers.Map: internal operation failed
Behavior
The output preserves the native class of numeric keys, including uint64 keys beyond binary64 exactness. The result is host-resident.
Execution and placement
Map storage and outputs are host-resident. Supported resident inputs gather only after compatibility and argument admission; map operations do not use GPU kernels or numeric fusion.
Map handles are local mutable identities backed by a runtime registry. Copying a handle is not a distributed transfer of the map.
Example
Exercise containers.Map.keys
m = containers.Map({'b','a'},{2,1});
k = keys(m);Using containers.Map.keys with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how containers.Map.keys changes the result.
Run a small containers.Map.keys example, explain the result, then change one input and compare the output.
FAQ
Is insertion order preserved?⌄
Do not rely on insertion order. RunMat returns keys in key order.
Related Containers functions
containers.Map · containers.Map.isKey · containers.Map.remove · containers.Map.subsasgn · containers.Map.subsref · containers.Map.values
Source you can read
Every RunMat function's source is public. Read exactly how containers.Map.keys is executed, line by line, in Rust.
- View the source for containers.Map.keys in Rust on GitHub
- Learn how the RunMat runtime works
- Found a bug? Open an issue with a minimal reproduction.
About RunMat
RunMat is a runtime that executes MATLAB-syntax code fast on any GPU. The runtime is free for individuals, including freelancers; students and faculty at an academic institution, for teaching or research there; contributors to an open-source project, for work on that project; organizations with 250 or fewer people and US$10M or less in annual revenue; and anyone, for non-production use. See runmat.com/license.
- RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
- Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.