You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
which makes this function less useful than it could be, since it means that all values held across await points must be Send. I don't think the Send requirement on the future is actually needed though? I forked leptos locally and removed it, and it still seems to compile and work properly.
Leptos Dependencies
leptos = { version = "0.7.0", features = ["csr"] }
Also checked my fork with the ssr feature in case there was a requirement for Sendness that only shows up when server-side rendering is enabled.
To Reproduce
Action::new_local(|()| asyncmove{let x = Rc::new(0);
futures_util::future::ready(()).await;*x
})
Expected behavior
This should compile.
Additional context
This came up in code ported from leptos 0.6, which has such a non-Send value being held across an await.
The text was updated successfully, but these errors were encountered:
Describe the bug
The signature of
Action::new_local
iswhich makes this function less useful than it could be, since it means that all values held across await points must be
Send
. I don't think theSend
requirement on the future is actually needed though? I forked leptos locally and removed it, and it still seems to compile and work properly.Leptos Dependencies
Also checked my fork with the
ssr
feature in case there was a requirement forSend
ness that only shows up when server-side rendering is enabled.To Reproduce
Expected behavior
This should compile.
Additional context
This came up in code ported from leptos 0.6, which has such a non-Send value being held across an await.
The text was updated successfully, but these errors were encountered: