rux-reactive 0.5.1

Rux reactivity core: signals and their values. Internal to Rux; the supported entry point is the ruxlang crate.
Documentation
  • Coverage
  • 61.9%
    13 out of 21 items documented0 out of 13 items with examples
  • Size
  • Source code size: 11.29 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 293.93 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 5s Average build duration of successful builds.
  • all releases: 4s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Aine-dickson/rux
    12 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • Aine-dickson

Rux's shared value type.

This crate began (M5) as the reactivity core: a flat Signals table plus a little expression evaluator. M8 replaced both with the rhai engine in rux-script, which owns state and evaluation now. What survives is Value , the untyped representation that rux-script and rux-style pass between each other for bindings, r-for locals, and props.

The per-binding subscription model in docs/04-architecture.md is now built (v0.3): rux-script tracks which signals each binding reads and which a handler writes, and rux-runtime patches/reconciles just the affected nodes in place instead of rebuilding the whole tree. This crate stays the shared Value type those layers pass around.