RunMat
GitHub

char — Convert numeric codes and text values into character arrays in MATLAB and RunMat.

char converts inputs into a character array. Numeric inputs are interpreted as code points, and text inputs are padded as needed so output rows share width, following MATLAB and RunMat conversion semantics.

Syntax

C = char()
C = char(X)
C = char(X...)

Inputs

NameTypeRequiredDefaultDescription
XAnyYesInput value to convert into character data.
X...AnyVariadicMultiple inputs converted row-wise and padded.

Returns

NameTypeDescription
CAnyCharacter array result.

Errors

IdentifierWhenMessage
RunMat:char:InvalidInputInput type cannot be converted to character data.char: invalid input
RunMat:char:InvalidCodePointNumeric input is not a finite integer Unicode code point.char: numeric inputs must be finite Unicode code points
RunMat:char:InvalidDimensionArray inputs are not 2-D (or trailing singleton dimensions).char: inputs must be 2-D
RunMat:char:InternalErrorInternal character array construction failed.char: internal error

How char works

  • char(x) with no arguments returns a 0×0 character array.
  • Numeric arrays must be real integers. The output character array has the same shape (up to two dimensions) as the numeric input.
  • String scalars and character vectors become individual rows. Rows are padded on the right with spaces to match the longest row.
  • String arrays with one or two dimensions contribute one row per element using MATLAB's column-major ordering.
  • Cell arrays must contain character vectors or string scalars. Each element becomes exactly one row in the result.
  • Inputs may be mixed and are vertically concatenated in the order they appear.
  • Complex inputs are unsupported and raise MATLAB-compatible errors.

Does RunMat run char on the GPU?

char gathers GPU tensors back to host memory using the active RunMat Accelerate provider before performing any conversion. The resulting character array always resides in host memory; providers do not need to supply specialised kernels.

GPU memory and residency

You usually do not need to call gpuArray manually for char. The runtime recognises that this builtin materialises text on the host, gathers GPU tensors automatically, and keeps the character array in CPU memory. Wrap the result in gpuArray(char(...)) only when you explicitly want the characters back on the device for subsequent GPU pipelines.

Examples

Converting a string scalar to a character row

name = char("RunMat")

Expected output:

name =
    'RunMat'

Building a character matrix from multiple rows

rows = char("alpha", "beta")

Expected output:

rows =
    'alpha'
    'beta '

Transforming numeric codes to characters

codes = [77 65 84 76 65 66];
letters = char(codes)

Expected output:

letters =
    'MATLAB'

Padding a string array into a character matrix

animals = ["cat"; "giraffe"];
C = char(animals)

Expected output:

C =
    'cat   '
    'giraffe'

Creating rows from a cell array of character vectors

dirs = {'north', 'east', 'west'};
chart = char(dirs)

Expected output:

chart =
    'north'
    'east '
    'west '

Converting GPU-resident codes back to text

G = gpuArray([82 85 78 77 65 84]);
label = char(G)

Expected output:

label =
    'RUNMAT'

Using char with coding agents

Open a RunMat example with live inputs, then ask the agent to explain how char changes the result.

Run a small char example, explain the result, then change one input and compare the output.

FAQ

Does char accept numeric arrays with more than two dimensions?

No. Numeric inputs must be scalars, vectors, or two-dimensional matrices. Higher-dimensional arrays raise an error so MATLAB's behaviour is preserved.

How are rows padded when lengths differ?

Each row is right-padded with space characters so every row in the result has the same width as the longest row that was produced.

Can I convert cell arrays that contain empty text?

Yes. Empty strings or character vectors become rows with zero columns; they still participate in padding when combined with longer rows.

What happens if a numeric value is not an integer?

The builtin rejects non-integer numeric values. Use round, floor, or uint32 beforehand if you need to convert floating-point values into valid code points.

Are code points above the Basic Multilingual Plane supported?

Yes. Any integer that represents a valid Unicode scalar value (0..0x10FFFF, excluding surrogates) is accepted and converted to the corresponding character.

Can char convert complex numbers?

No. Complex values are not supported because MATLAB also rejects them. Convert the data to real values before calling char.

Does char keep characters on the GPU?

No. After conversion the result is a CPU-resident character array. Use gpuArray(char(...)) if you need to move the result back to the device.

Open-source implementation

Unlike proprietary runtimes, every RunMat function is open-source. Read exactly how char is executed, line by line, in Rust.

About RunMat

RunMat is an open-source runtime that executes MATLAB-syntax code blazing on any GPU. It is licensed under the Apache 2.0 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.

Getting started · Benchmarks · Pricing

Download RunMat

Download RunMat for full performance, or use RunMat in your browser for zero setup.