ludic/docs/language/operators/op-compare.md
Orkuncakilkaya b7745a4600 refactor(lang): rename the str type (and stringify builtin) to string
Expand the abbreviated string type and its conversion builtin to the full
word everywhere:
  str            ->  string        (the immutable-string type)
  str(x) -> str  ->  string(x) -> string   (the stringify builtin;
                                            what `{…}` interpolation calls)

Types are recognized by identifier, and llty maps both spellings to LLVM
`ptr`, so this is an atomic source rewrite: type annotations, the Ludic
type tags, the builtin name/dispatch, and the interpolation desugar, plus
the grammars, LSP, docs (type-str -> type-string, fn-str -> fn-string), and
inventory. int/bool stay (universally accepted, like Math).

Reseeded; C-free fixpoint holds; all suites green (45/24/29); site + check.py OK.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-08-30 01:51:11 +03:00

868 B

id name category kind sig tip order
op-compare Comparison operators operator == != < <= > >= Compare two values and yield a bool; on strings == compares contents. 1

The comparison operators — == (equal), != (not equal), <, <=, >, >= — take two values and yield a bool, the kind of test an if or where clause wants. On string values == and != compare by content, so direction == "left" checks the characters, not the pointer (a comparison against null stays a pointer test). Comparison binds looser than arithmetic and looser than the bitwise operators, so flags & MASK == 0 reads as (flags & MASK) == 0 with no parentheses needed. Chain several conditions together with and / or.

if current_health <= 0 { become GameOver }
if pressed_key == 'w' and elapsed_frames > 0 { row = row - 1 }