Tsonic GitHub
Edit on GitHub

Numeric Types

Use @tsonic/core/types.js when CLR numeric intent matters.

Examples

import type { int, long, double, bool } from "@tsonic/core/types.js";

Common current types include:

  • byte
  • sbyte
  • short
  • ushort
  • int
  • uint
  • long
  • ulong
  • float
  • double
  • decimal
  • bool
  • char

Why not just number

number still exists, but it is not enough for every CLR-facing case.

You should use explicit numeric types when:

  • overload resolution depends on numeric width or signedness
  • emitted CLR APIs require exact types
  • precision or storage intent should be explicit

Examples:

import type { int } from "@tsonic/core/types.js";

const count: int = 1 as int;

import type { byte } from "@tsonic/core/types.js";

const bytes = new Uint8Array([1 as byte, 2 as byte]);

Practical guidance

  • use plain number for ordinary JS-surface arithmetic
  • use branded numeric types when CLR APIs, storage shape, or overload selection depend on the exact numeric kind
  • annotate public boundaries and sensitive overload calls first; you usually do not need to brand every local intermediate expression

Rule

Tsonic prefers explicit numeric intent over permissive conversion.