Skip to main content

Custom Enums (A | B)

There's two different types of enums - enum and unions.

TypeScript enums​

A TypeScript enum is essentially just an object where each key has an incrementing integer value, so Nitrogen will just generate a C++ enum natively, and bridges to JS using simple integers:

enum Gender {
  MALE,
  FEMALE
}
interface Person extends HybridObject<{ … }> {
  getGender(): Gender
}

This is efficient because MALE is the number 0, FEMALE is the number 1, and all other values are invalid.

TypeScript union​

A TypeScript union is essentially just variant of literal strings, which is only "typed" via TypeScript.

type Gender = 'male' | 'female'
interface Person extends HybridObject<{ … }> {
  getGender(): Gender
}

Nitrogen statically generates hashes for the strings "male" and "female" at compile-time, allowing for very efficient conversions between JS strings and native enums.

Unions need a name​

A TypeScript union consisting of only literal strings needs to be aliased to a separate type so that nitrogen can generate the native enum accordingly.

Bad ❌

interface Person extends HybridObject<{ … }> {
  getGender(): 'male' | 'female'
}
Good ✅
type Gender = 'male' | 'female'
interface Person extends HybridObject<{ … }> {
  getGender(): Gender
}