Hey, I am trying to write an async method that takes a closure as an argument and applies it to self. Included a minimal example: use futures::future::{self, BoxFuture}; use futures::Future; #[derive(std::fmt::Debug, Clone)] struct MyStruct { x: u32, } impl MyStruct { fn check<'a, F, T, F…

I'm not completely sure, but I think what's happening is this: As I wrote above, the problem is that the reference has to live as long as the future you return in the function passed to check. The solution I suggested above is to get rid of the reference to other_struct and not pass it into the clo…

Returning this value requires that `'1` must outlive `'2`

help

gendx November 28, 2020, 10:01am 10

I've found two related questions, and it seems that it's neither necessary to define a custom trait nor to use boxing, provided one can use the nightly #![feature(type_alias_impl_trait)].

Issue with FnOnce and async function with a &reference type argument
How to write a helper function to retry a future in a loop?

1 Like

Topic		Replies	Views
Lifetime with generic closure parameter returning a future help	4	225	March 22, 2024
Lifetime may not live long enough in async closure? help	5	769	September 24, 2023
Passing self to callback returning future vs lifetimes help	5	2584	March 29, 2021
Simple error: returning this value requires that `'1` must outlive `'2` help	3	1518	February 27, 2022
How to express that the Future returned by a closure lives only as long as its argument? help	14	2112	June 4, 2023

Returning this value requires that `'1` must outlive `'2`

Related Topics