From 475201ef6c1252c690973ed60dc6352aa0eb2d81 Mon Sep 17 00:00:00 2001 From: Luke Curley <432854+kixelated@users.noreply.github.com> Date: Thu, 12 Nov 2026 17:17:01 -0800 Subject: [PATCH 1/3] ci: queue and link from the kixel-ai org rust2 moved from moq-dev to kixel-ai. The queue build's reusable workflow ref, the crates' repository metadata, the driver's bug report URL, and every doc and quest link now name kixel-ai/rust2. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/queue.yml | 2 +- README.md | 2 +- bench/build/README.md | 6 +++--- driver/Cargo.toml | 2 +- driver/src/rustc.rs | 2 +- ffi/Cargo.toml | 2 +- go/Cargo.toml | 2 +- quest/m0/nightly-red.md | 14 +++++++------- quest/m0/object-cache-miss.md | 8 ++++---- quest/m1/README.md | 2 +- quest/m1/ffi-export/README.md | 10 +++++----- quest/m1/ffi-export/api-lock.md | 2 +- quest/m1/ffi-export/checks-raise.md | 4 ++-- quest/m1/ffi-export/copy-values.md | 4 ++-- quest/m1/ffi-export/lossless.md | 2 +- quest/m1/ffi-export/not-send.md | 4 ++-- quest/m1/ffi-refusals/README.md | 16 ++++++++-------- quest/m1/ffi-refusals/moq-main.md | 2 +- quest/m1/ffi-refusals/moq-pin.md | 8 ++++---- quest/m1/ffi-refusals/stale-excludes.md | 6 +++--- quest/m2/README.md | 4 ++-- quest/m2/ts-encode.md | 2 +- quest/m2/ts-iter-adaptors.md | 4 ++-- quest/m2/ts-model/README.md | 4 ++-- quest/m2/wasm/README.md | 4 ++-- quest/m3/README.md | 10 +++++----- quest/m3/relink.md | 6 +++--- quest/m3/session-quic.md | 2 +- quest/m3/tpde.md | 4 ++-- quest/m3/ts-tsrs.md | 2 +- quest/m3/ts-wasm-bindgen/README.md | 4 ++-- quest/m4/README.md | 6 +++--- quest/m4/fork.md | 6 +++--- quest/m4/go/README.md | 10 +++++----- quest/m4/go/coverage.md | 2 +- ts/Cargo.toml | 2 +- ts/README.md | 4 ++-- 37 files changed, 88 insertions(+), 88 deletions(-) diff --git a/.github/workflows/queue.yml b/.github/workflows/queue.yml index bf03d85e7..bc32daf1e 100644 --- a/.github/workflows/queue.yml +++ b/.github/workflows/queue.yml @@ -52,7 +52,7 @@ jobs: # reports its own context failed or cancelled, which fails the group. build: name: Queue build - uses: moq-dev/rust2/.github/workflows/queue-build.yml@main + uses: kixel-ai/rust2/.github/workflows/queue-build.yml@main # The merge queue still builds every group with the jobs above; this only # satisfies the PR-side requirement, as a pull_request run's skipped job does. diff --git a/README.md b/README.md index f4edcf1d7..f5729db85 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ Rust to other places. - **TypeScript**: an own rustc driver that translates a [documented Rust subset](ts/README.md) to TypeScript, without WASM. - **C, then any language**: an [exporter](ffi/README.md) that turns a crate's `pub` API into a C ABI and header with no attributes, sharing the TypeScript driver's front end. -- **Faster builds**: a reproducible [build-speed benchmark](bench/build/README.md) of upstream's levers on moq, and [rust2-lint](driver/src/bin/rust2-lint/main.rs), which fails a build whose generics' copies cost its codegen more than a budget (`nix run github:moq-dev/rust2#lint -- --help`). +- **Faster builds**: a reproducible [build-speed benchmark](bench/build/README.md) of upstream's levers on moq, and [rust2-lint](driver/src/bin/rust2-lint/main.rs), which fails a build whose generics' copies cost its codegen more than a budget (`nix run github:kixel-ai/rust2#lint -- --help`). Everything here is early; the [quest tree](quest/README.md) holds the plan. diff --git a/bench/build/README.md b/bench/build/README.md index 80c8bb19a..75dc615aa 100644 --- a/bench/build/README.md +++ b/bench/build/README.md @@ -63,7 +63,7 @@ The body edits are functions the program runs, which ra-jit compiles. ra-jit bugs seen on moq, not reported upstream: -- Async body edits in moq-net go to cargo (every `edit-async` run): "`parsed_values_given` is not compiled by ra-jit and rustc's copy is from before the edit: an instance of it does not compile", a generic of usage-argv's. The daemon then loads the workspace again: on CI such an edit took 50.6 s and 196 CPU-s, against plain cargo's 10.5 s and 14.5 CPU-s ([run](https://github.com/moq-dev/rust2/actions/runs/42351623273)). +- Async body edits in moq-net go to cargo (every `edit-async` run): "`parsed_values_given` is not compiled by ra-jit and rustc's copy is from before the edit: an instance of it does not compile", a generic of usage-argv's. The daemon then loads the workspace again: on CI such an edit took 50.6 s and 196 CPU-s, against plain cargo's 10.5 s and 14.5 CPU-s ([run](https://github.com/kixel-ai/rust2/actions/runs/42351623273)). - At the previous pin (`f36c848`), `cargo ra-jit check` with no build loaded read every crate of the workspace, took minutes and GBs, and failed on errors rustc does not report (`unresolved macro moq_clock::test` in moq-net's integration tests). - On a library-only build, `cargo ra-jit build` returns after `cargo clean` without building anything. @@ -102,7 +102,7 @@ Measured on 2026-10-25 and 2026-10-26 on a busy 32-CPU host, in billions of inst ## Cranelift for moq's CI Recommended on 2026-10-25: moq's CI keeps building its tests with LLVM, since 42 of its 5418 tests fail under Cranelift. -At the pin [#646](https://github.com/moq-dev/rust2/pull/646) moved to on 2026-11-07, 58 of 6379 fail: 27 that catch a panic and 31 on the intrinsic ([rustc_codegen_cranelift#1712](https://github.com/rust-lang/rustc_codegen_cranelift/issues/1712)). The numbers below are the 2026-10-25 run's. No retrial is planned once upstream fixes both: the saving below is the ceiling, and unwinding can only lower it. +At the pin [#646](https://github.com/kixel-ai/rust2/pull/646) moved to on 2026-11-07, 58 of 6379 fail: 27 that catch a panic and 31 on the intrinsic ([rustc_codegen_cranelift#1712](https://github.com/rust-lang/rustc_codegen_cranelift/issues/1712)). The numbers below are the 2026-10-25 run's. No retrial is planned once upstream fixes both: the saving below is the ceiling, and unwinding can only lower it. - 23 catch a panic, which the Cranelift backend that ships with nightly cannot unwind: it builds every panic as an abort (unwinding is a flag on cg_clif's own build, off by default: [rustc_codegen_cranelift#1567](https://github.com/rust-lang/rustc_codegen_cranelift/issues/1567)). - 19 abort on an x86 SIMD intrinsic it does not implement, `llvm.x86.sse2.pmulhu.w` ([rustc_codegen_cranelift#1712](https://github.com/rust-lang/rustc_codegen_cranelift/issues/1712), under the SIMD tracker [#171](https://github.com/rust-lang/rustc_codegen_cranelift/issues/171)). moq's CI runs on aarch64, whose intrinsics this x86 benchmark does not try. @@ -111,7 +111,7 @@ The `cranelift` variant's `build` numbers are for that abort build too. Since moq moved its crypto onto rind, the variant builds rind with LLVM: its `naked_asm!` takes `sym` operands, which Cranelift cannot compile yet ([rustc_codegen_cranelift#1620](https://github.com/rust-lang/rustc_codegen_cranelift/pull/1620)). Even passing, it would save little where CI spends its time. -CPU seconds from the [PR run](https://github.com/moq-dev/rust2/actions/runs/40235946635) (4 CPUs; an A/A control on that run stayed within 3%): +CPU seconds from the [PR run](https://github.com/kixel-ai/rust2/actions/runs/40235946635) (4 CPUs; an A/A control on that run stayed within 3%): | CI build | nightly | cranelift | change | | --- | ---: | ---: | ---: | diff --git a/driver/Cargo.toml b/driver/Cargo.toml index 95ac2ff56..f5aa3765f 100644 --- a/driver/Cargo.toml +++ b/driver/Cargo.toml @@ -4,7 +4,7 @@ description = "The rustc driver front end that rust2's drivers share, and rust2- version = "0.0.0" edition = "2024" license = "MIT OR Apache-2.0" -repository = "https://github.com/moq-dev/rust2" +repository = "https://github.com/kixel-ai/rust2" # A path dependency of the drivers, and rust2-lint through the flake: it only builds on # their pinned nightly. publish = false diff --git a/driver/src/rustc.rs b/driver/src/rustc.rs index 502c48e7e..7d1fbf2c0 100644 --- a/driver/src/rustc.rs +++ b/driver/src/rustc.rs @@ -7,7 +7,7 @@ use rustc_driver::Callbacks; use rustc_session::EarlyDiagCtxt; use rustc_session::config::ErrorOutputType; -const BUG_REPORT_URL: &str = "https://github.com/moq-dev/rust2/issues/new"; +const BUG_REPORT_URL: &str = "https://github.com/kixel-ai/rust2/issues/new"; /// Whether cargo ran this binary as its wrapper, which it does with the rustc it would /// have run as the first argument. diff --git a/ffi/Cargo.toml b/ffi/Cargo.toml index 3a1fb8f58..157866ea3 100644 --- a/ffi/Cargo.toml +++ b/ffi/Cargo.toml @@ -4,7 +4,7 @@ description = "Export a crate's pub API as a C ABI and header" version = "0.0.0" edition = "2024" license = "MIT OR Apache-2.0" -repository = "https://github.com/moq-dev/rust2" +repository = "https://github.com/kixel-ai/rust2" # Distributed through the flake: it only builds on the pinned nightly. publish = false diff --git a/go/Cargo.toml b/go/Cargo.toml index 61512499f..56173cb5e 100644 --- a/go/Cargo.toml +++ b/go/Cargo.toml @@ -4,7 +4,7 @@ description = "Translate a Rust subset to pure Go" version = "0.0.0" edition = "2024" license = "MIT OR Apache-2.0" -repository = "https://github.com/moq-dev/rust2" +repository = "https://github.com/kixel-ai/rust2" # Distributed through the flake: it only builds on the pinned nightly. publish = false diff --git a/quest/m0/nightly-red.md b/quest/m0/nightly-red.md index e9c0a4610..f8abc74ec 100644 --- a/quest/m0/nightly-red.md +++ b/quest/m0/nightly-red.md @@ -4,9 +4,9 @@ The nightly passes on `main`: its "Export moq-net to C" and "Export to Kotlin on Android" jobs, which failed in -[run 43246857664](https://github.com/moq-dev/rust2/actions/runs/43246857664) at `53d822ed` +[run 43246857664](https://github.com/kixel-ai/rust2/actions/runs/43246857664) at `53d822ed` on 2026-11-12, after -[run 43038758163](https://github.com/moq-dev/rust2/actions/runs/43038758163) passed at +[run 43038758163](https://github.com/kixel-ai/rust2/actions/runs/43038758163) passed at `936ce441` the day before. ## Plan @@ -17,17 +17,17 @@ Reproduce each before fixing it, at its root. - "Export moq-net to C" fails compiling `ffi/moq/moq.swift` under warnings as errors: the `Task(executorPreference: self, operation: body)` in `launch` is an unstructured throwing task whose result is unused. The job runs on arm64 Linux, where - [#711](https://github.com/moq-dev/rust2/pull/711) first ran the Swift, so name #711 + [#711](https://github.com/kixel-ai/rust2/pull/711) first ran the Swift, so name #711 under `## Caused by`. - "Export to Kotlin on Android" fails `api_android` at `ffi/tests/api.kt`'s `budgeted`: "the GC frees bytes lent once the budget is free". The ten commits between the two runs - include [#700](https://github.com/moq-dev/rust2/pull/700) and - [#708](https://github.com/moq-dev/rust2/pull/708); bisect on the emulator, and check + include [#700](https://github.com/kixel-ai/rust2/pull/700) and + [#708](https://github.com/kixel-ai/rust2/pull/708); bisect on the emulator, and check whether it fails every run before calling it a regression, since - [#693](https://github.com/moq-dev/rust2/pull/693) last fixed this test's lent bytes on + [#693](https://github.com/kixel-ai/rust2/pull/693) last fixed this test's lent bytes on ART. A test that depends on when the GC runs is fixed by making the collection deterministic, not by a retry. ## Closes -- [#716](https://github.com/moq-dev/rust2/issues/716) - the nightly's failure issue +- [#716](https://github.com/kixel-ai/rust2/issues/716) - the nightly's failure issue diff --git a/quest/m0/object-cache-miss.md b/quest/m0/object-cache-miss.md index 608d30bb1..488b89c2f 100644 --- a/quest/m0/object-cache-miss.md +++ b/quest/m0/object-cache-miss.md @@ -9,9 +9,9 @@ them from mbx's object cache, so the `mbx[cache]: object cache` line shows hits Two queue builds on the `nixos-rust2-ci` runner (nspawn container `rust2-ci` on `nixos`) compiled the same 55 crates and both logged 0 hits, 55 misses, 66.2 MiB stored locally: -[run 43265518031](https://github.com/moq-dev/rust2/actions/runs/43265518031) and -[run 43290025781](https://github.com/moq-dev/rust2/actions/runs/43290025781). A later one, -[run 43304642908](https://github.com/moq-dev/rust2/actions/runs/43304642908), got 17 hits +[run 43265518031](https://github.com/kixel-ai/rust2/actions/runs/43265518031) and +[run 43290025781](https://github.com/kixel-ai/rust2/actions/runs/43290025781). A later one, +[run 43304642908](https://github.com/kixel-ai/rust2/actions/runs/43304642908), got 17 hits of 204 lookups. Each job still used 9 to 19 CPU-minutes (the `quest-gate` scopes' `Consumed` CPU in the container journal, `journalctl -D /var/lib/nixos-containers/rust2-ci/var/log/journal` on `nixos`, not Actions wall time) against the 65 of the 2026-11-01 baseline, so the cache is headroom, not the gate's main saving. @@ -22,5 +22,5 @@ runs (paths, env, timestamps in the key). Reproduce by running the same build tw container and diffing the keys mbx logs. Fix at the root, and confirm with a queue build whose repeated crates hit. -Decided 2026-11-12 (maintainer, the pick of [#720](https://github.com/moq-dev/rust2/pull/720)): +Decided 2026-11-12 (maintainer, the pick of [#720](https://github.com/kixel-ai/rust2/pull/720)): ✅ keep this quest (rejected: drop it, since gate CPU already beats the baseline). diff --git a/quest/m1/README.md b/quest/m1/README.md index f9878e3e9..1aeccd499 100644 --- a/quest/m1/README.md +++ b/quest/m1/README.md @@ -8,7 +8,7 @@ builds its bindings with today. ## Plan Decided with the maintainer on 2026-10-25, from the -[spike](https://github.com/moq-dev/rust2/pull/41): the [exporter](/ffi/README.md), which +[spike](https://github.com/kixel-ai/rust2/pull/41): the [exporter](/ffi/README.md), which turns a crate's `pub` API into bindings with no attributes, replaces the UniFFI fork, whose feature quests are folded into the [exporter's](/quest/m1/ffi-export/README.md). diff --git a/quest/m1/ffi-export/README.md b/quest/m1/ffi-export/README.md index 95937ca12..52ff3d5eb 100644 --- a/quest/m1/ffi-export/README.md +++ b/quest/m1/ffi-export/README.md @@ -12,7 +12,7 @@ moq ships. It ends once every child has merged, the last of them ## Plan Decided with the maintainer on 2026-10-25, from the spike -([moq-dev/rust2#41](https://github.com/moq-dev/rust2/pull/41)): adopt the exporter, and fold +([kixel-ai/rust2#41](https://github.com/kixel-ai/rust2/pull/41)): adopt the exporter, and fold the fork's paused feature quests into it. Decided with the maintainer on 2026-10-27: this is an epic, with each item a child ranked by @@ -44,8 +44,8 @@ Decided with the maintainer on 2026-11-09, in the quest audit: Rejected: `#[doc(hidden)]` as the opt-out; exporting hidden items too. The Swift, Python, Go, and Dart generators landed in -[#406](https://github.com/moq-dev/rust2/pull/406), [#407](https://github.com/moq-dev/rust2/pull/407), -[#411](https://github.com/moq-dev/rust2/pull/411), and [#422](https://github.com/moq-dev/rust2/pull/422), +[#406](https://github.com/kixel-ai/rust2/pull/406), [#407](https://github.com/kixel-ai/rust2/pull/407), +[#411](https://github.com/kixel-ai/rust2/pull/411), and [#422](https://github.com/kixel-ai/rust2/pull/422), each generating the crate's own API in its language's idiom, as Kotlin does (decided with the maintainer on 2026-11-01). Only Python skips the C ABI, since a CPython extension calls about 40 times faster than `ctypes`; the others call C natively. @@ -78,7 +78,7 @@ Decided with the maintainer on 2026-11-12, in the quest audit: - ✅ The epic's closing work is a child, [ship](/quest/m1/ffi-export/ship.md), which alone requires [the refusals epic](/quest/m1/ffi-refusals/README.md). Rejected: the epic - requiring it, as [#701](https://github.com/moq-dev/rust2/pull/701) left it, since an + requiring it, as [#701](https://github.com/kixel-ai/rust2/pull/701) left it, since an epic's `Required` holds back every child, so none could start until moq's pin bump, which waits on a rind release the maintainer holds. - ✅ Every change that breaks the C ABI or a generated API is a child here, so it lands @@ -93,7 +93,7 @@ Decided with the maintainer on 2026-11-12, in the quest audit: Spike it on Go once they land. Decided with the maintainer on 2026-11-02 -([moq-dev/rust2#460](https://github.com/moq-dev/rust2/pull/460)): the RSS glibc's per-thread +([kixel-ai/rust2#460](https://github.com/kixel-ai/rust2/pull/460)): the RSS glibc's per-thread arenas keep under Go's lent `Bytes` is the consumer's to fix with its global allocator, as `ffi/README.md` documents. moq declares mimalloc in its exported crate, in its own tree. diff --git a/quest/m1/ffi-export/api-lock.md b/quest/m1/ffi-export/api-lock.md index 10e551b86..ead027805 100644 --- a/quest/m1/ffi-export/api-lock.md +++ b/quest/m1/ffi-export/api-lock.md @@ -22,7 +22,7 @@ first by kind and Rust path keeps the name and each later one takes a trailing ` old one, as `ffi/README.md` describes. With equal signatures a C caller compiles and calls the wrong function, and the contract hash only catches a header and library from different builds. Stable mangling was rejected when the naming rule was decided -([#599](https://github.com/moq-dev/rust2/pull/599)); this catches the break instead. +([#599](https://github.com/kixel-ai/rust2/pull/599)); this catches the break instead. - The baseline covers every target the binding serves. `--api` writes one target's API and refuses `--with` or a second `--target` (`ffi/src/cli.rs`), so a host-written file diff --git a/quest/m1/ffi-export/checks-raise.md b/quest/m1/ffi-export/checks-raise.md index 37c96cf12..d54ac3930 100644 --- a/quest/m1/ffi-export/checks-raise.md +++ b/quest/m1/ffi-export/checks-raise.md @@ -37,9 +37,9 @@ What the code does today: ([the binding benchmark](/bench/ffi/README.md)). - Kotlin and Go keep a hold count of their own beside the runtime's, so a call costs four atomic operations per handle. Swift keeps one only for its classes since - [#697](https://github.com/moq-dev/rust2/pull/697), and traps on a closed handle + [#697](https://github.com/kixel-ai/rust2/pull/697), and traps on a closed handle (`rt.swift`'s `hold`). The bindings' counts go; the runtime's status replaces them. -- [#700](https://github.com/moq-dev/rust2/pull/700) added a fourth check, an item called +- [#700](https://github.com/kixel-ai/rust2/pull/700) added a fourth check, an item called on a target the library is not built for, which traps in Swift (`ffi/src/swift.rs`) and panics in Go (`ffi/src/go.rs`). AGENTS.md lists three; add it there with this change. - Swift's `async throws` and throwing functions already exist for `Result`; a call that diff --git a/quest/m1/ffi-export/copy-values.md b/quest/m1/ffi-export/copy-values.md index 940ff182a..04171b5f1 100644 --- a/quest/m1/ffi-export/copy-values.md +++ b/quest/m1/ffi-export/copy-values.md @@ -22,7 +22,7 @@ more today in Kotlin, Python, Go, and Dart. - Prove it with the api fixture's differential tests and re-measure the bench. Decided with the maintainer on 2026-11-12, in the quest audit, for a size that differs by -target: since [#700](https://github.com/moq-dev/rust2/pull/700) one binding serves every +target: since [#700](https://github.com/kixel-ai/rust2/pull/700) one binding serves every target, moq ships 32-bit `armv7-linux-androideabi` beside 64-bit ones, and Kotlin, Python, and Dart share one source across them. @@ -37,7 +37,7 @@ and Dart share one source across them. staged API (`--api`) gains each such type's size and alignment per target, and the merge reads them. -What this replaces, from [#710](https://github.com/moq-dev/rust2/pull/710): the C ABI's +What this replaces, from [#710](https://github.com/kixel-ai/rust2/pull/710): the C ABI's `_copy`, the IR's `Object.copy`, and Swift's class for a `Copy` object. Public API: how every generated API holds a `Copy` type (breaking), and the staged API's diff --git a/quest/m1/ffi-export/lossless.md b/quest/m1/ffi-export/lossless.md index 073d7945f..259292d0d 100644 --- a/quest/m1/ffi-export/lossless.md +++ b/quest/m1/ffi-export/lossless.md @@ -38,7 +38,7 @@ What the audit found, each a place native Rust would have gone on: raises. - Integers: a Dart `u64` past `i64` reads negative; a Kotlin `usize` past a 32-bit target's aborts (`ffi/runtime/jni.rs`'s `narrow`) since - [#689](https://github.com/moq-dev/rust2/pull/689); and a Go `*big.Int` outside `u128` + [#689](https://github.com/kixel-ai/rust2/pull/689); and a Go `*big.Int` outside `u128` panics (`ffi_cgo.go`). - `Hash`: Dart's `hashCode` throws on a `PartialEq` type and Kotlin's returns 0; the IR carries no `Hash`. Export it where the type implements it. diff --git a/quest/m1/ffi-export/not-send.md b/quest/m1/ffi-export/not-send.md index 422c2a460..4ccccf05e 100644 --- a/quest/m1/ffi-export/not-send.md +++ b/quest/m1/ffi-export/not-send.md @@ -6,7 +6,7 @@ thread that made it: a call, poll, or drop from another thread never runs Rust code on that value there. Three of moq's own are refused for it at moq `ffcb7cd9`: `clock::Entered`, `clock::Rng`, and `catalog::Guard` -([#675](https://github.com/moq-dev/rust2/pull/675)). Proven per language by a fixture +([#675](https://github.com/kixel-ai/rust2/pull/675)). Proven per language by a fixture type holding an `Rc`, called, awaited, and dropped from a second thread. ## Plan @@ -36,7 +36,7 @@ an assert is fine "where a language has no concept of something being thread loc `@unchecked Sendable`, `ffi/src/swift.rs`). Confinement is not thread affinity, though: a Swift actor's jobs run on any thread of its pool, and a Dart isolate need not keep its OS thread, while Rust cannot tell an `Rc` from a guard pinned to its thread, as - [#675](https://github.com/moq-dev/rust2/pull/675) calls moq's three. So a `!Send` value needs the check or the owner thread below in + [#675](https://github.com/kixel-ai/rust2/pull/675) calls moq's three. So a `!Send` value needs the check or the owner thread below in Swift and Dart too, unless an executor pinned to the owner thread holds it; test a call after a suspension, and through Dart's relay. - Where a language has no stable thread, a Rust-owned thread holds the value and runs diff --git a/quest/m1/ffi-refusals/README.md b/quest/m1/ffi-refusals/README.md index cf3ebae85..27404aacd 100644 --- a/quest/m1/ffi-refusals/README.md +++ b/quest/m1/ffi-refusals/README.md @@ -17,7 +17,7 @@ fails the export rather than being excluded. ✅ Split: the naming rule first, t Rejected: one quest that waits for the census to reach zero. Decided with the maintainer on 2026-11-07, from -[moq-dev/rust2#655](https://github.com/moq-dev/rust2/pull/655): +[kixel-ai/rust2#655](https://github.com/kixel-ai/rust2/pull/655): - ✅ A whole-crate re-export (`pub use rustls;`) is refused with one span at its `pub use`, and moq drops its re-exports. A whole-crate re-export makes that crate's whole API part @@ -34,7 +34,7 @@ Decided with the maintainer on 2026-11-07, from [session-quic](/quest/m3/session-quic.md). Children leave the moq-tokio items outside that session side alone, since narrowing the stand-in drops them. - Narrowing the stand-in was to land first; the 2026-11-09 audit dropped that order, and - [moq-dev/rust2#683](https://github.com/moq-dev/rust2/pull/683) narrowed it. + [kixel-ai/rust2#683](https://github.com/kixel-ai/rust2/pull/683) narrowed it. - ✅ What C can never hold, an object no export returns or lends to a closure, or a generic type no export instantiates, is left out of the bindings and kept listed in the census. Rejected: refusing them, which would make moq add constructors it has no use for. @@ -42,7 +42,7 @@ Decided with the maintainer on 2026-11-07, from covers. Decided with the maintainer on 2026-11-09, from -[moq-dev/rust2#678](https://github.com/moq-dev/rust2/pull/678): +[kixel-ai/rust2#678](https://github.com/kixel-ai/rust2/pull/678): - ✅ rust2 asks moq for no source changes: changing moq is a non-goal, so every refusal that waited on moq changing a signature gets an answer on rust2's side. moq's merged @@ -54,14 +54,14 @@ Decided with the maintainer on 2026-11-09, from The census at moq `ffcb7cd9` (2026-11-07) refused 1111 items, which `ffi/moq/ffi.toml`'s 347 excludes hide by naming whole modules. About 790 lay in crates moq re-exports whole, -which [#668](https://github.com/moq-dev/rust2/pull/668) has since made one refusal each, -and [#671](https://github.com/moq-dev/rust2/pull/671) moved what C can never hold out of +which [#668](https://github.com/kixel-ai/rust2/pull/668) has since made one refusal each, +and [#671](https://github.com/kixel-ai/rust2/pull/671) moved what C can never hold out of the refusals, so the figures below predate both. The other 324 are moq's own, 107 of them in moq-tokio (61 under `quic`); each child gives its construct's count, and an item counts under every construct it hits. The counts include the moq-tokio items narrowing drops; each child measures again once it lands. 17 more refuse only because a type they name is refused, and clear with it. After the stand-in narrows -([moq-dev/rust2#683](https://github.com/moq-dev/rust2/pull/683)), the census refuses 130 +([kixel-ai/rust2#683](https://github.com/kixel-ai/rust2/pull/683)), the census refuses 130 items, 41 of them in moq-tokio, and 6 types. Decided with the maintainer on 2026-11-12, in the quest audit: @@ -71,9 +71,9 @@ Decided with the maintainer on 2026-11-12, in the quest audit: building for wasm32, which only the translator needs. Rejected: one pin for both, at the cost of two revisions to bump. - The last per-construct child landed in - [#710](https://github.com/moq-dev/rust2/pull/710), yet the Goal is not reached: the + [#710](https://github.com/kixel-ai/rust2/pull/710), yet the Goal is not reached: the 2026-11-11 nightly census - ([run 43038758163](https://github.com/moq-dev/rust2/actions/runs/43038758163)) still + ([run 43038758163](https://github.com/kixel-ai/rust2/actions/runs/43038758163)) still refuses 94 items and 5 types at the pin, behind `ffi/moq/ffi.toml`'s 100 excludes, and moq's `main` adds the 36 errors [the pin bump](/quest/m1/ffi-refusals/moq-pin.md) measured. So each construct left has a child again: diff --git a/quest/m1/ffi-refusals/moq-main.md b/quest/m1/ffi-refusals/moq-main.md index 1de4a9b3f..438c096bc 100644 --- a/quest/m1/ffi-refusals/moq-main.md +++ b/quest/m1/ffi-refusals/moq-main.md @@ -22,7 +22,7 @@ can never hold is left out and listed. - Recommended for a third-party type by value: an opaque handle with none of its API, as the `Arc` form already is, since the value moves into the handle exactly. - Recommended for the borrowing future of a non-async fn: the rule async fns' borrowing - futures already follow ([#710](https://github.com/moq-dev/rust2/pull/710)). + futures already follow ([#710](https://github.com/kixel-ai/rust2/pull/710)). - No exclude is added to `ffi/moq/ffi.toml` to pass. Public API: the generated API of each item that newly exports. diff --git a/quest/m1/ffi-refusals/moq-pin.md b/quest/m1/ffi-refusals/moq-pin.md index 310523dbc..0c352a6a4 100644 --- a/quest/m1/ffi-refusals/moq-pin.md +++ b/quest/m1/ffi-refusals/moq-pin.md @@ -6,14 +6,14 @@ The moq pin moves to moq's current `main`, whose crates re-export no whole crate included. `just ffi census` there lists no whole-crate re-export refusal. Its "type not reachable from the crate root" refusals are `kio::Pending` and `lite::version::Version`, which the exporter change below exports, and moq-quic's stats and varint types under moq-tokio's `quic::driver`, -which [moq-dev/rust2#683](https://github.com/moq-dev/rust2/pull/683) drops. At `ffcb7cd9` there were 20 such refusals (18 Guard and Side, and +which [kixel-ai/rust2#683](https://github.com/kixel-ai/rust2/pull/683) drops. At `ffcb7cd9` there were 20 such refusals (18 Guard and Side, and `Version`), and 9 at moq's head on 2026-11-09, measured in -[#676](https://github.com/moq-dev/rust2/pull/676). +[#676](https://github.com/kixel-ai/rust2/pull/676). ## Plan Decided with the maintainer on 2026-11-07, from -[moq-dev/rust2#655](https://github.com/moq-dev/rust2/pull/655) and +[kixel-ai/rust2#655](https://github.com/kixel-ai/rust2/pull/655) and [moq-dev/moq#8233](https://github.com/moq-dev/moq/pull/8233): ✅ moq re-exports no whole crate, its own included: the ten first listed (moq-net's `bytes` and `kio`; `rustls` in moq-quic, moq-rtmp, and moq-tokio; moq-tokio's `notify`, `usage_rs`, and `http`; @@ -46,7 +46,7 @@ moq-tokio's `quic::driver` items, which the narrowed stand-in drops. Then bump the pin in `ts/fixtures/model/Cargo.toml`, which `ts/justfile`'s `moq_rev` reads, and report the census before and after. The last bump -([#390](https://github.com/moq-dev/rust2/pull/390)) also changed `ffi/moq/ffi.toml`, every +([#390](https://github.com/kixel-ai/rust2/pull/390)) also changed `ffi/moq/ffi.toml`, every `ffi/moq/moq.*`, and rust2-ts's model fixture, bench, and expected output, which share the pin: run `just ts census` too, and update the count in the [model epic](/quest/m2/ts-model/README.md). diff --git a/quest/m1/ffi-refusals/stale-excludes.md b/quest/m1/ffi-refusals/stale-excludes.md index 59ee22692..32c5d7920 100644 --- a/quest/m1/ffi-refusals/stale-excludes.md +++ b/quest/m1/ffi-refusals/stale-excludes.md @@ -10,12 +10,12 @@ and `just ffi moq` builds everything that maps. Found by the 2026-11-12 audit, comparing the file against the 2026-11-11 nightly census's "config that exports what maps" -([run 43038758163](https://github.com/moq-dev/rust2/actions/runs/43038758163)): 28 of the +([run 43038758163](https://github.com/kixel-ai/rust2/actions/runs/43038758163)): 28 of the 100 excludes name items that export, such as `Path::from_static`, the `Timestamp::as_*` conversions, `mux::Source`'s methods, and `varint::encode_quic`, so `just ffi moq` never builds what -[#675](https://github.com/moq-dev/rust2/pull/675) and -[#678](https://github.com/moq-dev/rust2/pull/678) made exportable. At moq's `main`, 11 +[#675](https://github.com/kixel-ai/rust2/pull/675) and +[#678](https://github.com/kixel-ai/rust2/pull/678) made exportable. At moq's `main`, 11 more name nothing exported ([the pin bump](/quest/m1/ffi-refusals/moq-pin.md)). Measure both again first. diff --git a/quest/m2/README.md b/quest/m2/README.md index 6c8a82146..990dbae33 100644 --- a/quest/m2/README.md +++ b/quest/m2/README.md @@ -30,12 +30,12 @@ Decided with the maintainer on 2026-11-12, in the quest audit: [the gate's measurement](/quest/m2/wasm/routes.md) requires, and [a spike of the per-call crossing](/quest/m2/wasm/crossing-spike.md), which says before the backend lands whether wasm's lead survives it. On the 2026-11-12 nightly - ([run 43246857664](https://github.com/moq-dev/rust2/actions/runs/43246857664), Chromium) + ([run 43246857664](https://github.com/kixel-ai/rust2/actions/runs/43246857664), Chromium) the translation ran about 5 times wasm's time on compute, geometric mean over 82 rows. Rejected: the spike alone, with fixes frozen behind the gate; judging the translator as it stands. - ✅ [The model epic](/quest/m2/ts-model/README.md) moves to m3 with a `Required` on the - gate, since once [#722](https://github.com/moq-dev/rust2/pull/722) merges its only + gate, since once [#722](https://github.com/kixel-ai/rust2/pull/722) merges its only content is a wait on moq, which m3 holds. Not moved yet: #722 holds its branch, and `quest mv` refuses a claimed quest. Rejected: keeping it in m2. diff --git a/quest/m2/ts-encode.md b/quest/m2/ts-encode.md index 306a2f13d..d8f1bfb09 100644 --- a/quest/m2/ts-encode.md +++ b/quest/m2/ts-encode.md @@ -5,7 +5,7 @@ [rust2-ts](/ts/README.md) translates `to_be_bytes`, `to_le_bytes`, and a literal byte array that flow only into `extend_from_slice` or `put_slice` as direct stores, with no typed array made per write. On the 2026-11-12 nightly -([run 43246857664](https://github.com/moq-dev/rust2/actions/runs/43246857664), Chromium) a +([run 43246857664](https://github.com/kixel-ai/rust2/actions/runs/43246857664), Chromium) a QUIC varint encode costs 13.6 ns at one byte, 56.2 at two, and 194 at eight, against wasm's 4.84, 9.14, and 9.65, and a video frame encode 289 against 33.7. diff --git a/quest/m2/ts-iter-adaptors.md b/quest/m2/ts-iter-adaptors.md index 25a619677..1a7e6c94a 100644 --- a/quest/m2/ts-iter-adaptors.md +++ b/quest/m2/ts-iter-adaptors.md @@ -5,7 +5,7 @@ A report says whether lowering an iterator chain's adaptors (`map`, `filter`, `zip`, `enumerate`) to code of its own, with leaf iterators left in the runtime, closes the iterator workloads' gap. On the 2026-11-12 nightly -([run 43246857664](https://github.com/moq-dev/rust2/actions/runs/43246857664), Chromium) +([run 43246857664](https://github.com/kixel-ai/rust2/actions/runs/43246857664), Chromium) the iterator family ran 12.9 times wasm's time: `zip-map-filter-count` 56.4 ns against 2.84 hand-written, and `enumerate-for` 12.2 against 1.89. If the spike earns it, this quest is rewritten to the landing work and sized again. @@ -19,7 +19,7 @@ Decided with the maintainer on 2026-11-12, in the quest audit: ✅ before the ga type and V8 stops inlining them. Confirm it with a profile before changing anything. - `ts/README.md`'s design rejected lowering adaptors from core's MIR because slice iterators are raw pointers. This keeps leaf iterators in the runtime and specializes - only the adaptors, as [#129](https://github.com/moq-dev/rust2/pull/129) did for + only the adaptors, as [#129](https://github.com/kixel-ai/rust2/pull/129) did for `Option`'s and `Result`'s combinators. - Hand-edit one `iter/` workload's output and compare it through `--route name=dir`, in Chrome and Firefox, with the bundle's size, which grows per chain. diff --git a/quest/m2/ts-model/README.md b/quest/m2/ts-model/README.md index 247ab04bf..028bd661c 100644 --- a/quest/m2/ts-model/README.md +++ b/quest/m2/ts-model/README.md @@ -69,12 +69,12 @@ it here, as pointer identity already translates as JS identity; that is on the g path. Decided with the maintainer on 2026-11-04, from a census at the bumped pin -(moq-dev/rust2#390): the refusals no quest owned became child quests, since finished. +(kixel-ai/rust2#390): the refusals no quest owned became child quests, since finished. ✅ arrayvec's `ArrayString` needs three of them (const generic types, `begin_panic`, `str::as_ptr`), kept separate since each lands alone; rejected: one quest for `ArrayString`. Decided with the maintainer on 2026-11-07, after three designs for addresses as identity -([#596](https://github.com/moq-dev/rust2/pull/596)) each left values whose ids were never freed +([#596](https://github.com/kixel-ai/rust2/pull/596)) each left values whose ids were never freed or pointers whose comparison disagreed with Rust after an address was reused: - ✅ Addresses stay refused: every read of a pointer's address as an integer (`as usize`, diff --git a/quest/m2/wasm/README.md b/quest/m2/wasm/README.md index 1dd3f69c6..18836e60e 100644 --- a/quest/m2/wasm/README.md +++ b/quest/m2/wasm/README.md @@ -31,8 +31,8 @@ Decided with the maintainer on 2026-11-09, in the quest audit: other targets planned ahead of a consumer are. Rejected: one `wasm32-wasip1` module for both, with the binding implementing its imports. - ✅ m2, with per-target export in m1, which landed in - [#689](https://github.com/moq-dev/rust2/pull/689) and - [#700](https://github.com/moq-dev/rust2/pull/700). Rejected: all of it in m1; all of it + [#689](https://github.com/kixel-ai/rust2/pull/689) and + [#700](https://github.com/kixel-ai/rust2/pull/700). Rejected: all of it in m1; all of it in m2. - ✅ Until the gate reports, translator work is only what the gate needs: the model's remaining refusals and the benchmark. [m3](/quest/m3/README.md#plan) records what waits. diff --git a/quest/m3/README.md b/quest/m3/README.md index 3ac6a6c7e..40400aa02 100644 --- a/quest/m3/README.md +++ b/quest/m3/README.md @@ -49,7 +49,7 @@ Decided with the maintainer on 2026-11-12, in the quest audit: positives; a general semver checker, which cargo-semver-checks is taking into cargo; a Rust generator over the C ABI as a rebuild firewall; and driver-generated derives, since proc macros measured 0.2% of a clean build - ([#64](https://github.com/moq-dev/rust2/pull/64)). + ([#64](https://github.com/kixel-ai/rust2/pull/64)). Decided with the maintainer on 2026-11-07, the unsafe policy, to stop one-off fixes for ever rarer `unsafe`: @@ -69,12 +69,12 @@ ever rarer `unsafe`: 5. ✅ Where translation can't see where an `unsafe` pointer came from, a loud run-time check stands in for the refusal, the exception AGENTS.md names: `ptrUnerase`, `offset_from` across arrays, `AtIndex.reach`, and raw slices of a field's byte - (decided 2026-11-07 in [#661](https://github.com/moq-dev/rust2/pull/661) and - [#621](https://github.com/moq-dev/rust2/pull/621)). Safe code gets no such check: it + (decided 2026-11-07 in [#661](https://github.com/kixel-ai/rust2/pull/661) and + [#621](https://github.com/kixel-ai/rust2/pull/621)). Safe code gets no such check: it translates exactly or is refused. Rejected: an unsafe std gap with no consumer becoming its own quest, as `MaybeUninit::zeroed`, `Rc::new_uninit`, and `ptr::write_bytes` would have -([#647](https://github.com/moq-dev/rust2/pull/647)), or as `Vec::from_raw_parts`'s adopted -storage did ([#635](https://github.com/moq-dev/rust2/pull/635)); and a second, byte-backed +([#647](https://github.com/kixel-ai/rust2/pull/647)), or as `Vec::from_raw_parts`'s adopted +storage did ([#635](https://github.com/kixel-ai/rust2/pull/635)); and a second, byte-backed memory model for values whose address is reinterpreted, without a consumer. diff --git a/quest/m3/relink.md b/quest/m3/relink.md index b88c0bef7..6e0554bb5 100644 --- a/quest/m3/relink.md +++ b/quest/m3/relink.md @@ -9,10 +9,10 @@ variant on moq's edits. ## Plan It is the one upstream lever the moq-net edit leaves room for. The figures below are from -moq before its poll-first rewrite: [#646](https://github.com/moq-dev/rust2/pull/646) has +moq before its poll-first rewrite: [#646](https://github.com/kixel-ai/rust2/pull/646) has since moved the benchmark's pin past it, and numbers across a pin bump do not compare, so measure again before relying on them. The benchmark's -attribution ([run](https://github.com/moq-dev/rust2/actions/runs/40093020939)) +attribution ([run](https://github.com/kixel-ai/rust2/actions/runs/40093020939)) puts 4.5 s of that edit's 6.95 s critical path in crates rebuilt only because moq-net changed, 0.6 s of it the final link that would remain. Cranelift and the parallel frontend move the edit within noise; the backend is 6% of its @@ -37,7 +37,7 @@ What decides whether this lever ever pays on moq: the pinned nightly, and a different rust#156940 hash, so a cutoff keyed on either needs that fixed first. -The [semantic API hash replay](https://github.com/moq-dev/rust2/pull/62) +The [semantic API hash replay](https://github.com/kixel-ai/rust2/pull/62) (2026-10-25) hashed only what a dependent can reach and observe, over the same edits. Differential tests show it sound, and it held on 18 of 250 non-test edits under moq's dev profile (17 of 169 on PR branches, 1 of 81 squash merges): diff --git a/quest/m3/session-quic.md b/quest/m3/session-quic.md index 216381455..9383a2305 100644 --- a/quest/m3/session-quic.md +++ b/quest/m3/session-quic.md @@ -18,7 +18,7 @@ moq-tokio, which `ffi/moq/moq.c` proves with moq-tokio's fallback runtime. It su with their own event loop or sockets. Decided with the maintainer on 2026-10-28, from -[#215](https://github.com/moq-dev/rust2/pull/215): at moq `30f25c04`, only moq-tokio's +[#215](https://github.com/kixel-ai/rust2/pull/215): at moq `30f25c04`, only moq-tokio's and moq-uring's drivers join moq-quic to moq-net's `poll::Session`, and each brings a runtime. The runtime-free driver that joins them is moq's change, not the exporter's. Datagrams move by pull: the binding passes in each one it receives, polls on each wake and diff --git a/quest/m3/tpde.md b/quest/m3/tpde.md index 3772f6303..bb4cf1719 100644 --- a/quest/m3/tpde.md +++ b/quest/m3/tpde.md @@ -14,7 +14,7 @@ Decided with the maintainer on 2026-11-07: m4. Decided with the maintainer on 20 in the quest audit: ✅ m3, with upstream's other build-speed levers (rejected: m4). What it targets, from the subset-compiler report -([moq-dev/rust2#615](https://github.com/moq-dev/rust2/pull/615)) at moq main: +([kixel-ai/rust2#615](https://github.com/kixel-ai/rust2/pull/615)) at moq main: LLVM is 21% of a clean build's rustc self-time and 28% of a non-incremental moq-net edit's (36% with building the IR, which TPDE does not replace), almost all of it O0 machine-code emission. The incremental edit spends 0.1% in LLVM, @@ -30,7 +30,7 @@ instructions by 16% clean and 25% on the non-incremental edit. build instead. Report the fallback count. - Recommended: list it in the moq job in [bench.yml](/.github/workflows/bench.yml) beside `cranelift`. That job runs only on dispatch or a harness change since - [#686](https://github.com/moq-dev/rust2/pull/686), so a later upstream gain shows only + [#686](https://github.com/kixel-ai/rust2/pull/686), so a later upstream gain shows only at the next pin bump. - The nightly bump here is the benchmark's own (`flake.nix`'s `rust-bin.nightly`), a corpus change that lands apart from the variant (`bench/build/corpus.toml`). diff --git a/quest/m3/ts-tsrs.md b/quest/m3/ts-tsrs.md index 6fe32b61a..9cadaea95 100644 --- a/quest/m3/ts-tsrs.md +++ b/quest/m3/ts-tsrs.md @@ -10,7 +10,7 @@ failing at the Rust span as today, and measures the translation's time against r ## Plan Decided with the maintainer on 2026-10-27, on -[the bindings PR](https://github.com/moq-dev/rust2/pull/127): translation runs the +[the bindings PR](https://github.com/kixel-ai/rust2/pull/127): translation runs the flake's `tsc` 7 for now. tsrs was experimental then, and its reported speed over TypeScript 7 is the vendor's own. diff --git a/quest/m3/ts-wasm-bindgen/README.md b/quest/m3/ts-wasm-bindgen/README.md index f0da460ab..ea0f40094 100644 --- a/quest/m3/ts-wasm-bindgen/README.md +++ b/quest/m3/ts-wasm-bindgen/README.md @@ -9,7 +9,7 @@ import becoming a direct JS call, so Rust developers keep using idiomatic Rust c instead of JS types. web-rs's web-codecs translates end to end as a stock crate, its decoders and audio included, which is this quest's remaining work: the [encoder fixture](/ts/fixtures/encoder/Cargo.toml) proves a `VideoEncoder`'s calls on a -copy of web-codecs' encoder ([#681](https://github.com/moq-dev/rust2/pull/681)), not on +copy of web-codecs' encoder ([#681](https://github.com/kixel-ai/rust2/pull/681)), not on the crate. Non-goals: `#[wasm_bindgen]` exports, since a translation already exports the crate's `pub` @@ -56,7 +56,7 @@ Decided with the maintainer on 2026-11-06: wasm32 clock over js-sys first, a moq change made only for translation. - ✅ Translation reads each import's JS shape from the program the macro encodes in a `link_section` static, not from the `extern` blocks' source. The - [spike](https://github.com/moq-dev/rust2/pull/638) has the measurements: + [spike](https://github.com/kixel-ai/rust2/pull/638) has the measurements: `macro_rules!`-made imports, which source reading misses, are on the encoder's path. - ✅ web-codecs' encoders and decoders also hand their frames and errors through tokio's `sync::mpsc` and `sync::watch`, which translation refused then (about 50 refusals in diff --git a/quest/m4/README.md b/quest/m4/README.md index e44efdf3c..9c2ea6cc0 100644 --- a/quest/m4/README.md +++ b/quest/m4/README.md @@ -14,12 +14,12 @@ Declined on 2026-10-25: a drop-in build-cache wrapper with an early cutoff. The cutoff is unsound on stock rustc (a stale SVH gives E0460, and DefIndex shifts), mbx and cargo already cover caching and GC, and a sound cutoff holds on only 7% of moq-net edits -([moq-dev/rust2#62](https://github.com/moq-dev/rust2/pull/62), -[moq-dev/rust2#70](https://github.com/moq-dev/rust2/pull/70)). +([kixel-ai/rust2#62](https://github.com/kixel-ai/rust2/pull/62), +[kixel-ai/rust2#70](https://github.com/kixel-ai/rust2/pull/70)). [The fork](/quest/m4/fork.md) collects the reasons to change rustc and cargo instead. Closed on 2026-11-06: a compiler for a stricter Rust subset -([moq-dev/rust2#615](https://github.com/moq-dev/rust2/pull/615)). 61% of the +([kixel-ai/rust2#615](https://github.com/kixel-ai/rust2/pull/615)). 61% of the LLVM IR moq's own crates emit is std's and dependencies' generics instantiated at moq's types, closures included, so it would have to compile std too. Levers that need no new frontend reach its best case: ra-jit already applies the diff --git a/quest/m4/fork.md b/quest/m4/fork.md index 1bfdbeeac..135924343 100644 --- a/quest/m4/fork.md +++ b/quest/m4/fork.md @@ -27,7 +27,7 @@ Each names what the fork changes, the measured gain on moq, and its source. under pipelining ([rust-lang/cargo#17439](https://github.com/rust-lang/cargo/issues/17439)). Gain: the replay estimates a cutoff holds on about 65 of 250 non-test moq-net edits in dev (26%), up from a sound 18 (7%), but on only 7 of 84 async edits - ([moq-dev/rust2#62](https://github.com/moq-dev/rust2/pull/62)). The + ([kixel-ai/rust2#62](https://github.com/kixel-ai/rust2/pull/62)). The estimate approximates the side table with `debug = 0` and `-Z location-detail=none`, which no differential test covers, so the fork's semantics need their own before this counts as sound. Each skip saves at most @@ -37,14 +37,14 @@ Each names what the fork changes, the measured gain on moq, and its source. ### Not reasons - **A drop-in `RUSTC_WRAPPER` cutoff**, declined on 2026-10-25 - ([moq-dev/rust2#70](https://github.com/moq-dev/rust2/pull/70)): + ([kixel-ai/rust2#70](https://github.com/kixel-ai/rust2/pull/70)): - it is unsound on stock rustc: a skipped dependent keeps its dependency's old SVH, so the next crate fails with E0460, and its rmeta encodes the dependency's DefIndex raw, which shifts; - caching, GC, and dedup are already in mbx, and cargo's cross-workspace cache goal is in progress; - its sound cutoff holds on 7% of moq-net edits - ([moq-dev/rust2#62](https://github.com/moq-dev/rust2/pull/62)). + ([kixel-ai/rust2#62](https://github.com/kixel-ai/rust2/pull/62)). Public API: none until the fork has a consumer. diff --git a/quest/m4/go/README.md b/quest/m4/go/README.md index 5cf4dbfd8..94d7fbe37 100644 --- a/quest/m4/go/README.md +++ b/quest/m4/go/README.md @@ -13,12 +13,12 @@ plain install and cross-compiling, so a pure-Go moq is worth researching. The cg exporter stays moq's Go route until a translation matches it. Decided with the maintainer on 2026-11-01, settling -[#410](https://github.com/moq-dev/rust2/pull/410): +[#410](https://github.com/kixel-ai/rust2/pull/410): - **Continue as research,** speed first, then [coverage](/quest/m4/go/coverage.md). If speed cannot bring the translated crate within 2x of cgo on a realistic whole-crate workload (a group's stream end to end, - decided on 2026-11-02 in [#428](https://github.com/moq-dev/rust2/pull/428)), delete + decided on 2026-11-02 in [#428](https://github.com/kixel-ai/rust2/pull/428)), delete `go/` and this epic, keeping the measurements in the PR that does. - **Share rust2-ts's front end piece by piece,** as Go needs each piece, starting with the control-flow structuring, now `driver/src/cfg.rs`. No shared crate lands ahead @@ -26,7 +26,7 @@ Decided with the maintainer on 2026-11-01, settling whose lowering returns TypeScript's AST. Decided with the maintainer on 2026-11-07, settling -[moq-dev/rust2#643](https://github.com/moq-dev/rust2/pull/643): +[kixel-ai/rust2#643](https://github.com/kixel-ai/rust2/pull/643): - **Speed met the bar.** With the translation owning a `Vec`'s storage and clipping it at escape, every `stream/` workload of `just go bench` runs within 2x of cgo, the @@ -39,7 +39,7 @@ Decided with the maintainer on 2026-11-07, settling Rejected: splitting [coverage](/quest/m4/go/coverage.md) into a quest per construct now; deleting `go/`, whose translator and measurements are kept. -The spike ([moq-dev/rust2#410](https://github.com/moq-dev/rust2/pull/410)) translated +The spike ([kixel-ai/rust2#410](https://github.com/kixel-ai/rust2/pull/410)) translated moq's codec held to rust2-ts's bar: 35,273 codec cases and 124,193 integer cases match native Rust, panics included. On 2026-11-01 it ran 2 to 113 times slower than cgo on batched loops, which #643 above superseded. Stripped, it adds 324 KB to a Go binary where @@ -51,7 +51,7 @@ Decided with the maintainer on 2026-11-12, in the quest audit: ([its quest](/quest/m0/go-nightly.md)). Rejected: keeping it in the gate; deleting `go/`, which stays rejected. - ✅ The four Go API quests planned from - [#614](https://github.com/moq-dev/rust2/pull/614)'s follow-ups are folded in here as + [#614](https://github.com/kixel-ai/rust2/pull/614)'s follow-ups are folded in here as notes, since none can start while the epic is parked and each rewrote the same `go/fixtures/items`. Their full text is in git history, last at `bf5ca258`, under `quest/m4/go/`. When the epic resumes, plan them again in this order: diff --git a/quest/m4/go/coverage.md b/quest/m4/go/coverage.md index 9d583088b..6a41d5fa0 100644 --- a/quest/m4/go/coverage.md +++ b/quest/m4/go/coverage.md @@ -35,7 +35,7 @@ failed speed result deletes `go/`, so planning the constructs earlier would be w The last coverage child reruns `just go bench` against speed's bar, every `stream/` workload within 2x of cgo, since constructs such as `Vec::capacity` change what the stream workload runs. Speed reached the bar on 2026-11-07 in -[moq-dev/rust2#643](https://github.com/moq-dev/rust2/pull/643), but the epic is parked +[kixel-ai/rust2#643](https://github.com/kixel-ai/rust2/pull/643), but the epic is parked until a consumer needs pure Go, so the split waits for that too. - ✅ Gate on speed, split later. diff --git a/ts/Cargo.toml b/ts/Cargo.toml index a65dc9712..e1172f0c0 100644 --- a/ts/Cargo.toml +++ b/ts/Cargo.toml @@ -34,7 +34,7 @@ resolver = "3" [workspace.package] edition = "2024" license = "MIT OR Apache-2.0" -repository = "https://github.com/moq-dev/rust2" +repository = "https://github.com/kixel-ai/rust2" [workspace.lints.rust] # What rust2-ts sets where it translates, for a safe twin of `unsafe`. diff --git a/ts/README.md b/ts/README.md index 134e04106..37e84c4eb 100644 --- a/ts/README.md +++ b/ts/README.md @@ -1050,7 +1050,7 @@ they need. - A `String` is an `rs.String`, its text as a JS string beside its UTF-8 length and capacity, rather than a bare JS string, which holds no capacity, or UTF-8 bytes, which every `Display` and JS boundary would decode. Measured on - [#574](https://github.com/moq-dev/rust2/pull/574), it matched or beat a JS string at + [#574](https://github.com/kixel-ai/rust2/pull/574), it matched or beat a JS string at encoding, decoding, and joining, and cost 7-22% writing lines and up to 2.3x in a map keyed by one, where UTF-8 bytes cost 5.6-9.8x. A `&str` and a `Box` stay JS strings, which hold all they do. @@ -1182,7 +1182,7 @@ they need. so `append` is O(1) and `split_off` walks from the nearer end; each node is the place `iter_mut` and `front_mut` lend of an item JS copies. Dropping a whole hash map or set drops its entries in the runtime's order, not hashbrown's: std leaves that order undocumented - ([#272](https://github.com/moq-dev/rust2/pull/272)). Maintainer's decision on 2026-10-30. + ([#272](https://github.com/kixel-ai/rust2/pull/272)). Maintainer's decision on 2026-10-30. A whole B-tree drops as std's `drop_tree` does, node by node in postorder, and its `IntoIter` in key order, as std's does. - A slice's `sort` and `sort_unstable` are std's driftsort and ipnsort, ported to the From 47d1740ebbc87da82a85772c4c09802da7e05766 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 20:16:50 -0800 Subject: [PATCH 2/3] quest(m0): api_swift waits for an async closure's timeout error Co-Authored-By: Claude Opus 5.5 --- quest/m0/swift-gives-up.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 quest/m0/swift-gives-up.md diff --git a/quest/m0/swift-gives-up.md b/quest/m0/swift-gives-up.md new file mode 100644 index 000000000..b0cabe7ce --- /dev/null +++ b/quest/m0/swift-gives-up.md @@ -0,0 +1,19 @@ +# [XS] api_swift waits for the error an async closure's timeout raises + +## Goal + +`api_swift` in `ffi/tests/fixtures.rs` passes every run: its "Rust gives up on an async +closure" check in `ffi/tests/api.swift` no longer fails intermittently. + +## Plan + +Found while validating [#740](https://github.com/kixel-ai/rust2/pull/740) on 2026-11-13: +`just ffi test --test fixtures` failed `api_swift` there in 2 of 4 runs, and at `main` +`7008d1d3` in 1 of 5, each time with `"futures" failed: Rust gives up on an async closure`. +The test passes alone. + +The check reads `threw` after a single `q.drain()`, so it fails if the task's resumption +with `within(0)`'s `Overflow` error reaches the queue after `drain` returned, as it can +when the Rust future is polled off the queue. The check above it already waits with +`until { q.drain(); return got.value != 0 }`; confirm the race first, such as by delaying +the resumption, then wait the same way rather than retrying the test. From 058503f45b2a359287dcc47a7669f530b6b20c46 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 20:22:52 -0800 Subject: [PATCH 3/3] quest(m0): the swift test's closure must stay pending too Co-Authored-By: Claude Opus 5.5 --- quest/m0/swift-gives-up.md | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/quest/m0/swift-gives-up.md b/quest/m0/swift-gives-up.md index b0cabe7ce..dd5650f5a 100644 --- a/quest/m0/swift-gives-up.md +++ b/quest/m0/swift-gives-up.md @@ -12,8 +12,17 @@ Found while validating [#740](https://github.com/kixel-ai/rust2/pull/740) on 202 `7008d1d3` in 1 of 5, each time with `"futures" failed: Rust gives up on an async closure`. The test passes alone. -The check reads `threw` after a single `q.drain()`, so it fails if the task's resumption -with `within(0)`'s `Overflow` error reaches the queue after `drain` returned, as it can -when the Rust future is polled off the queue. The check above it already waits with -`until { q.drain(); return got.value != 0 }`; confirm the race first, such as by delaying -the resumption, then wait the same way rather than retrying the test. +Two races fit, and the fix covers both: + +- The closure is empty, so it can finish before the budget runs out: `Pollable.poll` in + `ffi/runtime/rt.swift` starts the closure's Task and then loads `done` again, and + `Within::poll` in `ffi/fixtures/api/src/lib.rs` polls the inner future before checking + its budget. When the Task finishes in that window, `within(0) {}` returns `Ok(())` and + nothing throws. The closure must stay pending, such as by awaiting a stream nothing + yields to, as the check above it does. +- The check reads `threw` after a single `q.drain()`, so it also fails if the task's + resumption with the `Overflow` error reaches the queue after `drain` returned. The check + above it waits with `until { q.drain(); return got.value != 0 }`; wait the same way. + +Confirm which one fails before fixing, such as by delaying the closure's Task or the +resumption, and fix the test's timing rather than retrying it.