[01]
k4 language
Verbs, adverbs, lists, dictionaries, tables, and control forms — the first target.
- atomic vectors
- nested lists
- dicts and keyed tables
- function application
[ COMPAT ] k and q surface
same programs. new runtime.
l runs existing k4, q, and qSQL workloads without source changes. The preview focuses on local execution, benchmark reproduction, and compatibility reports.
current target
k4 + q + qSQL
Measured against real code paths: tables, symbols, temporal data, query forms, and the execution model.
preview platform
osx arm64
next reports
q/k behavior
[ MATRIX ] language coverage
compatibility surface.
[02]
q and qSQL
q syntax and qSQL, validated against real analytical workloads, not isolated examples.
- select / exec / update
- grouped aggregations
- temporal columns
- symbol-heavy tables
[03]
IPC surface
The protocol boundary, tested for local services and remote execution.
- hopen-style connections
- request / response
- remote query strings
- typed payloads
[04]
runtime behavior
The engine picks scalar, SIMD, threaded, or compressed paths while preserving behavior.
- numeric reductions
- compressed vectors
- parallel scans
- deterministic results
[ PLATFORMS ] binary status
platform validation.
| platform | binary | validation | notes |
|---|---|---|---|
| osx arm64 | available | primary research preview | apple silicon local execution |
| linux x64 | planned | benchmark target | used for commodity server comparisons |
| linux arm64 | planned | compatibility pass pending | represented in release tree |
[ REPORTS ] edge cases wanted
send the weird cases.
The best reports isolate a single behavior difference. Small examples beat large applications.
- the smallest k or q snippet that reproduces it
- the l version and host platform
- the expected behavior or output
- whether the issue is parser, type, query, IPC, or performance related
next step
report a compatibility gap.
Use the contact form for behavior differences, parser failures, IPC notes, and benchmark issues.
Contact the team