lab/sx

Files

agra 989e18b760 feat: tuple syntax cutover — Tuple(...) type + .(...) value

Replace the bare-paren tuple grammar with explicit, position-unambiguous
forms, mirroring how structs work:

  type     `(A, B)`        -> `Tuple(A, B)`          (named keeps `:`)
  value    `(a, b)`        -> `.(a, b)`              (named uses `=`)
  typed    (new)           -> `Tuple(A, B).(a, b)`   (like `Point.{...}`)
  failable `-> (T, !)`     -> `-> T !`
           `-> (T1, T2, !)`-> `-> Tuple(T1, T2) !`   (channel outside Tuple)

Bare `(...)` is now grouping only, everywhere; a comma in bare parens is a
hard error with a migration hint. Grouping, function types `(A, B) -> R`,
param lists, lambdas, and match bindings are unaffected.

`Tuple(...)` is strictly a TYPE in every position (including `size_of` /
`type_info` args); a tuple VALUE comes only from `.(...)` (anonymous) or
`Tuple(...).(...)` (explicitly typed). A bare `Tuple(1, 2)` is a tuple
type with non-type elements -> rejected.

The ~110 tuple-bearing corpus files were migrated with a one-shot
AST-aware migrator (the `sx migrate` tool from the prior commit, removed
here). New examples: 0130 (new syntax), 0131 (typed construction), 1060
(named-tuple failable return). 1116 golden updated for the new hint text.

2026-06-25 17:53:57 +03:00

library: vendors/sqlite — SQLite ships with sx

2026-06-12 17:39:26 +03:00

README.md

library: vendors/sqlite — SQLite ships with sx

2026-06-12 17:39:26 +03:00

sqlite.sx

feat: tuple syntax cutover — Tuple(...) type + .(...) value

2026-06-25 17:53:57 +03:00

README.md

vendors/sqlite — SQLite for sx programs

Version: 3.53.2 (SQLITE_VERSION in c/sqlite3.h)
Source: https://sqlite.org/2026/sqlite-amalgamation-3530200.zip
Zip sha256: 8a310d0a16c7a90cacd4c884e70faa51c902afed2a89f63aaa0126ab83558a32
Files kept: c/sqlite3.c, c/sqlite3.h (the amalgamation; shell.c and sqlite3ext.h dropped — no shell, no loadable extensions)
License: public domain (https://sqlite.org/copyright.html)

#import "vendors/sqlite/sqlite.sx" gives any sx program SQLite with no system dependency and no build flags. The bindings declare the amalgamation as a named #import c unit carrying the pinned compile options (SQLITE_DQS=0, SQLITE_THREADSAFE=0, SQLITE_DEFAULT_MEMSTATUS=0, SQLITE_OMIT_DEPRECATED, SQLITE_OMIT_SHARED_CACHE, SQLITE_LIKE_DOESNT_MATCH_BLOBS, SQLITE_ENABLE_COLUMN_METADATA, -O2); sx compiles the unit through its content-addressed object cache (.sx-cache/), so the 250k-line source builds once per machine. sx build links the objects into the binary; sx run loads them as a PRIORITY symbol-search target ahead of the process images, so an OS libsqlite3 of a different version can never shadow this copy. examples/1624-vendor-sqlite-module.sx pins the version and a typed round trip in the sx suite.

Bound surface

sqlite.sx maps the full practical C API (~100 functions): connection lifecycle + open_v2 flags, errors (extended codes included), statements with the complete bind/column families, parameter and column introspection (built with SQLITE_ENABLE_COLUMN_METADATA), incremental blob I/O, the online backup API, serialize/deserialize, and the library utilities. Not bound, by design: callback-taking APIs (hooks, UDFs, collations, authorizers — they need C→sx callbacks), the sqlite3_value_* family (UDF-coupled), varargs configuration, UTF-16 variants, and subsystems this build omits (mutex/VFS under SQLITE_THREADSAFE=0, sessions/snapshots/vtabs, deprecated API).

To upgrade: replace c/sqlite3.c/c/sqlite3.h with a newer amalgamation, update this file and the version pins in consuming test suites, and rebuild (the object cache keys on the source bytes, so the new amalgamation recompiles automatically).