Orkuncakilkaya
2c9f9ac549
Phase 1 of the fuller type-system proposal: two by-value spatial types that lower to packed integers (no heap, copy like scalars). - IVec2 — integer 2D vector, a pair of int packed into one i64, for tile and grid coordinates: make/zero/x/y/add/sub/scale/dot, the grid distance manhattan, equal, and to_vector (widen into the fixed-point Vector). - Rect — axis-aligned rectangle, four Q16.16 fixed components packed into one i128, for HUD boxes and hitboxes: make/x/y/w/h, the derived right/bottom/center, and the contains (point) / intersects (overlap) tests. Both are exact and deterministic, bit-identical on every platform. Vector and Color already cover phase 1's other 2D primitives. Wired end to end: emit_core llty (IVec2->i64, Rect->i128), emit_call dispatch, the FRAGS list + reseeded seed, a selfhost test (types2d), per-symbol docs + type pages + inventory, and the vocabulary/editor sync (header, JetBrains, TextMate, LSP). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
22 lines
576 B
Markdown
22 lines
576 B
Markdown
---
|
|
id: rect-contains
|
|
name: Rect.contains
|
|
category: rect
|
|
kind: namespace-method
|
|
tokens: Rect.contains
|
|
sig: Rect.contains(r, px, py) -> bool
|
|
tip: True when the point is inside.
|
|
order: 8
|
|
ns: Rect
|
|
member: contains
|
|
---
|
|
|
|
Tests whether the point <code>(px, py)</code> falls inside the rectangle. The left and top edges are inclusive; the right and bottom edges are exclusive, so adjacent rectangles tile without overlap. The classic use is a mouse-in-button hit test.
|
|
|
|
```ludic
|
|
program Demo {
|
|
handler Step phase Update {
|
|
if Rect.contains(button, mx, my) { press() }
|
|
}
|
|
}
|
|
```
|