Files
craft-libs/crates/develop
texjer dcb3fcf603 craft-develop: inpaint rejects an impossible patch radius, and one cancelled poll cancels the call
Review fixes. A patch radius near usize::MAX overflowed in 2 * r + 1; an image with no pixels and a
huge height walked every empty row; a cancellation seen only by a worker's poll was dropped, so a
half-finished pass could come back as a result.
2026-11-18 09:33:47 -05:00
..

craft-develop

The raw develop pipeline, CPU path: the shared pipeline of #587, moved from LightCraft one module at a time. No unsafe, no panics on hostile input, no file I/O, and it builds for wasm32-unknown-unknown.

craft-develop = { git = "https://github.com/storytold/craft-libs", rev = "<commit>" }

What is here

Module From LightCraft (a75497d6) Contents
inpaint crates/inpaint Content-aware hole filling for spot removal: complete (multi-scale patch completion with PatchMatch) and membrane_fill (a smooth harmonic fill, its seed and fallback). Interleaved f32 buffers of any channel count, a fixed-seed RNG, the same result on any number of threads.

Parity with LightCraft

Each module comes with a test that its output is LightCraft's at the base commit, compared with craft-render-parity at Tolerance::BASELINE. The expected pictures in tests/fixtures/ were written by LightCraft's own crate at that commit, on the scene the test builds.

Where the code differs from LightCraft's, the output for every input LightCraft handled is the same:

  • inpaint::complete_with returns None for a patch radius wider than the image before computing with it (LightCraft reaches the same None, or overflows on a huge radius), returns an image with no pixels at once, and reports Cancelled when any one poll said so, including a poll made on a worker thread.

Not here yet

The rest of the pipeline: colour, raster, the sensor stage, raw loading and the render stages. No app uses this crate yet.