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>
31 lines
853 B
Markdown
31 lines
853 B
Markdown
---
|
|
id: text-equals
|
|
name: Text.equals
|
|
category: text
|
|
kind: namespace-method
|
|
tokens: Text.equals
|
|
sig: Text.equals(a, b) -> bool
|
|
tip: Whether two strings have identical bytes.
|
|
order: 7
|
|
ns: Text
|
|
member: equals
|
|
---
|
|
|
|
Returns <code>true</code> when <code>a</code> and <code>b</code> hold the same bytes in the same order. This is a value comparison, not a pointer check, and is exactly what the <code>==</code> operator does between two strings — <code>Text.equals</code> is the named form for readability. Use it to match input against a keyword or compare a slice with an expected token.
|
|
|
|
Parameters:
|
|
- `a` — the first string
|
|
- `b` — the second string
|
|
|
|
```ludic
|
|
program Guess {
|
|
var answer: string = "swordfish"
|
|
var attempt: string = "swordfish"
|
|
|
|
handler Check phase Update {
|
|
if Text.equals(attempt, answer) {
|
|
# correct
|
|
}
|
|
}
|
|
}
|
|
```
|