rux-reactive 0.6.0

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: 12.74 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 294.01 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 7s 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-reactive

Value, the untyped representation that the rest of Rux passes around for bindings, r-for locals and component props.

The crate began as Rux's reactivity core, a flat signal table plus a small expression evaluator. Both were replaced by the rhai engine in rux-script, which owns state and evaluation now, and by the per-binding subscription model in rux-runtime, which patches only the nodes a changed signal actually reaches. What survives here is the shared value type those layers hand to each other, which is why the crate is much smaller than its name suggests.

Internal to Rux

This is one crate of the Rux workspace. It is published so the toolchain builds from crates.io, not as a library to depend on: it makes no stability promise of its own and its API moves whenever the runtime needs it to. The supported entry point is ruxlang.

cargo install ruxlang     # installs a `rux` command

rux run app.rux

ruxlang.dev · learn · reference · try it in a browser

Licence

Dual licensed under Apache-2.0 or MIT, at your option.