Change the semantics of exprs/for loops allocations strategy
This commit adjusts how exprs and for loops are handled within rsx. This is a breaking change in terms of codegen, but has slight semantic changes as well. Now, when exprs/for loops are allocated, they are given a temporary. The temporary is elided to the <'a> lifetime of the bump, to satisfy the borrow checker. This fixes issues with signals where exprs/for loops mapping vecs out of RefCells would be caught up without a temporary lifetime.
This commit is contained in:
2 files changed
+24
-4
No files matched your search
@@ -7,6 +7,7 @@ fn main() {
|
||||
|
||||
fn app(cx: Scope) -> Element {
|
||||
let mut count = dioxus_signals::use_signal(cx, || 0);
|
||||
let saved_values = dioxus_signals::use_signal(cx, || vec![0]);
|
||||
|
||||
use_future!(cx, || async move {
|
||||
loop {
|
||||
@@ -19,9 +20,19 @@ fn app(cx: Scope) -> Element {
|
||||
h1 { "High-Five counter: {count}" }
|
||||
button { onclick: move |_| count += 1, "Up high!" }
|
||||
button { onclick: move |_| count -= 1, "Down low!" }
|
||||
button {
|
||||
onclick: move |_| saved_values.push(count.value()),
|
||||
"Save this value"
|
||||
}
|
||||
|
||||
// We can do boolean operations on the current signal value
|
||||
if count.value() > 5 {
|
||||
rsx!{ h2 { "High five!" } }
|
||||
}
|
||||
|
||||
// We can cleanly map signals with iterators
|
||||
for value in saved_values.read().iter() {
|
||||
h3 { "Saved value: {value}" }
|
||||
}
|
||||
})
|
||||
}
|
||||
Reference in new issue
Block a user