This crate provides the Fate type, which can be used to create thread-safe reactive declarations. Fate instances that depend on other Fate values will automatically update their values when a dependency is altered. The crate also includes a macro for automatically creating and updating Fate instances.
Disclaimer: Extremely alpha, possibly broken, definitely changing.
fate! {
[name] // Name will be accessed as a Fate value
// All assignments in the macro will be treated as Fate types
let name = "Alex".to_string();
let hello = "Hello, ".to_string() + &name;
let goodbye = "Goodbye, ".to_string() + &name;
}
assert_eq!(&hello.get(), "Hello, Alex");
assert_eq!(&goodbye.get(), "Goodbye, Alex");
fate! {name = "Sam".to_string();}
assert_eq!(&hello.get(), "Hello, Sam");
assert_eq!(&goodbye.get(), "Goodbye, Sam");
use fates::{fate, Fate};
fate! {
[a] // a is accessed as a Fate type.
let a = 5;
let b = a * 3;
}
assert_eq!(b.get(), 15);
fate! {a = 7;}
assert_eq!(a.get(), 7);
assert_eq!(b.get(), 21);
let a = 1;
let b = 10;
let c = 15;
fate! {
[d]
let d = a + b; // 1 + 10
let e = d * c; // 11 * 15
}
assert_eq!(e.get(), 11 * 15);
fate! {d = a;}
assert_eq!(e.get(), 15);
fate! {
let a = vec![1, 2, 3];
}
assert_eq!(a.get(), vec![1, 2, 3]);
a.by_ref_mut(|a| a.push(4));
assert_eq!(a.get(), vec![1, 2, 3, 4]);
let mut val = 2;
a.by_ref(|a| val = a[2]);
assert_eq!(val, 3);
If an expression is bound, by_ref / by_ref_mut will not run the supplied function. You can check for this:
fate! {
[a]
let a = 5;
let b = a * 5;
}
{
let mut is_value = false;
a.by_ref_mut(|_a| {
is_value = true;
});
assert_eq!(is_value, true);
}
{
let mut is_value = false;
b.by_ref_mut(|_b| {
is_value = true;
});
assert_eq!(is_value, false);
}
struct TestStruct {
fate: Fate<i32>,
}
fate! {
let a = 10;
}
let test_struct = TestStruct { fate: a.clone() };
assert_eq!(a.get(), 10);
fate! {a = 15;}
assert_eq!(test_struct.fate.get(), 15);
// Alternatively:
a.bind_value(200);
assert_eq!(test_struct.fate.get(), 200);
fate! {
[a]
let a = 5;
let b = a + 3;
}
let child = b.create_dependent_clone();
assert_eq!(child.get(), 8);
fate! {
a = 10;
}
assert_eq!(b.get(), 13);
assert_eq!(b.is_dirty(), false);
// Even though b is no longer dirty, the dependent clone is still dirty.
// This can be used to do something locally whenever the Fate is updated.
assert_eq!(child.is_dirty(), true);
assert_eq!(child.get(), 13);
assert_eq!(child.is_dirty(), false);
- The "destiny operator": https://paulstovell.com/reactive-programming/.
- Reactive declarations in Svelte.