functions — Inspect a function handle's current RunMat metadata.
functions(fh) returns a scalar struct with function, type, and file fields for a function handle or closure. This is diagnostic metadata, not a stable serialization format.
Syntax
info = functions(fh)Inputs
fh- Type
Callable- Required
- Yes
- Default
- —
- Description
- Function handle or closure.
Returns
info- Type
Any- Description
- Function-handle metadata struct.
Errors
RunMat:FunctionsHandleUnsupported- When
- The input is not a supported function handle value.
- Message
functions: expected a function handle
Behavior
Named and external handles report their name and simple type. Source-bound handles use compiler-owned primary/local/nested/anonymous role metadata, and return the registered source path when available. An unbound closure without typed compiler provenance reports unknown rather than guessing its role from its display name.
All three fields are RunMat string scalars. MATLAB's metadata can include additional fields and closure workspace details; those are not currently represented.
Non-handle inputs raise RunMat:FunctionsHandleUnsupported before resident-provider access.
Execution
This portable native/browser metadata query does not invoke the handle or its captured values. It does not gather a resident payload and has no whole-call transfer schedule of its own.
Example
Inspect a named handle
fh = @sin; info = functions(fh);Using functions with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how functions changes the result.
Run a small functions example, explain the result, then change one input and compare the output.
FAQ
Can I rely on the metadata for program logic?⌄
No. The structure is intended for inspection; source provenance and additional MATLAB fields are not currently represented.
Related Introspection functions
addlistener · addParameter · addprop · assignin · builtin · cancel · class · clear · clearAllMemoizedCaches · clearCache · clearvars · dbclear · dbstack · dbstatus · dbtype · eval · evalc · evalin · feval · findprop · func2str · get.p · getcallinfo · getmethod · inputname · inputParser · isa · ischar · isdeployed · iskeyword · ismethod · isobject · isstring · isUnderlyingType · isvalid · keyboard · loadobj · localfunctions · matlab.metadata.DynamicProperty.delete · memoize · metaclass · mfilename · mislocked · mlock · munlock · namelengthmax · narginchk · nargoutchk · new_object · notify · numArgumentsFromSubscript · onCleanup · parse · saveobj · set.p · stats · str2func · subsasgn · subsref · superclasses · underlyingType · verLessThan · version · which · who · whos
Source you can read
Every RunMat function's source is public. Read exactly how functions is executed, line by line, in Rust.
- View the source for functions 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.