roxlap-core 0.1.1

Pure-Rust port of Ken Silverman's Voxlap voxel engine — engine core.
Documentation
[package]
name = "roxlap-core"
version.workspace = true
edition.workspace = true
license.workspace = true
repository.workspace = true
authors.workspace = true
rust-version.workspace = true
readme.workspace = true
description = "Pure-Rust port of Ken Silverman's Voxlap voxel engine — engine core."
documentation = "https://docs.rs/roxlap-core"
keywords = ["voxlap", "voxel", "renderer", "raycaster", "engine"]
categories = ["game-development", "graphics", "rendering::engine"]

[dependencies]
# R6: meltsphere builds Kv6 sprites from world voxel data; the Kv6
# type lives in the formats crate alongside the parser/serialiser.
# Path used during local development; version is what cargo publish
# records for downstream resolution.
roxlap-formats = { path = "../roxlap-formats", version = "0.1" }

# R12.2.1: rayon's par_iter for the per-strip / per-row / per-sprite
# parallel rendering paths. Single-threaded callers
# (`ScratchPool::new`) skip the parallel branch entirely; rayon's
# default thread pool only warms up when the parallel branch fires.
#
# R10.X.2: rayon now works on wasm32 too via wasm-bindgen-rayon's
# Web-Worker-backed thread pool — the host crate (`roxlap-web` or
# `roxlap-cave-web`) re-exports `wasm_bindgen_rayon::init_thread_pool`
# so JS can `await initThreadPool(N)` before any rayon-using code
# runs. Builds need `-Z build-std` (nightly) +
# `-Ctarget-feature=+atomics,+bulk-memory,+mutable-globals` —
# see `.cargo/config.toml` and `rust-toolchain.toml` for the
# pinned setup.
rayon = { workspace = true }

[dev-dependencies]
# R6.0e: integration test loads the gzipped oracle.vxl fixture and
# compares roxlap's meltsphere output against the byte-dumped C
# oracle sprites in tests/fixtures/.
flate2 = { version = "1", default-features = false, features = ["rust_backend"] }

[lints]
workspace = true