Rust's safety rests on five guarantees. JavaScript already has one, memory, thanks to the garbage collector. strict-ts
brings the other four, one rule at a time. This table is the project's scoreboard.
| Rust guarantee | Equivalent in TS/JS | Status |
| Memory safety | The runtime's garbage collector | Acquired |
Safe typing, nothing unchecked outside unsafe | No any, cast, declare or @ts-ignore outside unsafe/; a // SAFETY: reason inside | Acquired |
| No null, errors in the types | Option, Result, no-throw, must-use; a call or an operator that may throw is caught where it is written | Acquired |
| Explicit mutability | Types read-only unless they say Mut<T>. A function changes only what it made, or what says Mut: a parameter, this, what another function hands out | Prototype |
| Ownership, no uncontrolled concurrent access | A value typed Once<T> has one owner and is given away exactly once (use-once). State shared across await and workers: nothing yet | Research: a first rule, on a small subset |
« Acquired » has a narrow meaning here: no way around the guarantee is known in checked code. Each way that was
found is a file that fails when it is run, kept in the tests with the rule that refuses it: 32 for safe typing, 29
for errors in the types. It is a list and not a proof, the lists were written by who wrote the rules, and what is
taken on trust (the specification as it was read, the browser as it was run, the types of the packages a project
allows) is in Known limits. « Prototype » means the rules exist and are tested, and ways
around them are still being found: explicit mutability went from 2 known ways refused to 83 in nineteen rounds, the
last seventeen after an application had already been made to pass, and no round has yet found nothing.