SplitScript reference / Migration / Bounded native stringN state

Bounded native stringN state

Migration from ASL

Source pattern

Look for the ASL concept Bounded native stringN state in the source. The semantic difference below is more important than a token-for-token rewrite.

Canonical SplitScript

Use the canonical language and API symbols linked below.

Semantic difference

Choose the native encoding explicitly: utf8 bounds bytes and utf16le bounds two-byte code units.

Supported hosts

This uses the standard SplitScript runtime contract. Any provider-specific requirements are documented by the linked canonical API.