Indexed. Use of moved value

[ghost]

Please tell me what is the best way to write something like this so that there is no error?

(use of moved value: value.foo
move occurs because value.foo has type std::string::String, which does not implement the Copy traitrustcE0382)

use sycamore::prelude::*;

#[derive(Clone, PartialEq)]
struct Foo {
    foo: String,
}

#[component]
fn Test<G: Html>(cx: Scope) -> View<G> {
    let values = create_signal(cx, vec![] as Vec<Foo>);

    view! { cx,
            Indexed(
                iterable=values,
                view=|cx, value| view! { cx,
                    div(data-value=value.foo) { (value.foo) }
                }
            )
    }
}

[ghost]

Is it ok to use create_ref like this?

Indexed(
    iterable=values,
    view=|cx, value| {
        let value = create_ref(cx, value);
        view! { cx,
            div(data-value=value.foo) { (value.foo) }
        }
    }
)

[lukechu10]

Yup that works great.

[ghost]

won't there be memory leaks if the vector is frequently overwritten (loaded from the network)?

[lukechu10]

won't there be memory leaks if the vector is frequently overwritten (loaded from the network)?

No because the cx refers to the one inside the closure so it's destroyed every time that row changes.

[nicmr]

@lukechu10 The accepted solution does not work anymore in sycamore >= 0.9.0-beta2, since create_ref was removed from sycamore_reactive. How would we handle this now?

[lukechu10]

The simplest here would just be to clone the string. If that is not acceptable, you can always put it into a Rc but that is almost never the case since the overhead of sending the string to JS will outweigh many times any cost of cloning the string.