localfunctions — Return handles to named local functions in the current source file.
localfunctions() returns a 1-by-N cell row of bound function handles in the current source file. With no source context it returns a 1-by-0 cell array.
Syntax
handles = localfunctions()Returns
handles- Type
Any- Description
- Cell row of visible local function handles.
Errors
RunMat:TooManyInputs- When
- Any input argument is provided.
- Message
localfunctions: too many input arguments
Current source
The runtime queries compiler-owned source-function roles, retaining only Local handles and excluding the primary function, nested functions, anonymous functions, methods, and synthetic entrypoints. It does not scan arbitrary files or execute a handle.
The result is a cell row in the runtime catalog's current order. MATLAB does not promise handle order; do not rely on a particular ordering across source/catalog changes.
Input arguments are not accepted and raise RunMat:TooManyInputs. The current runtime does not separately identify script, function-file, nested, and command-line contexts with MATLAB's full semantics.
Execution
Native and browser runtimes use the same source-function catalog. Handles remain bound to their source-local function identities and are not provider payloads. Transfer to a worker requires that source/function identity to be available there.
Example
Find a named local function
handles = probe_locals();Using localfunctions with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how localfunctions changes the result.
Run a small localfunctions example, explain the result, then change one input and compare the output.
FAQ
Does it return an ordered list of names?⌄
No. It returns a cell row of bound function handles; source/catalog order is not a portable sorting guarantee.
Related Introspection functions
addlistener · addParameter · addprop · assignin · builtin · cancel · class · clear · clearAllMemoizedCaches · clearCache · clearvars · dbclear · dbstack · dbstatus · dbtype · eval · evalc · evalin · feval · findprop · func2str · functions · get.p · getcallinfo · getmethod · inputname · inputParser · isa · ischar · isdeployed · iskeyword · ismethod · isobject · isstring · isUnderlyingType · isvalid · keyboard · loadobj · 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 localfunctions is executed, line by line, in Rust.
- View the source for localfunctions 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.