Question for @rustlang folks: have you ever had a function signature that needed multiple [non-static] lifetimes where collapsing them into one wouldn’t work? Aren’t all lifetimes just ‘the length of this function call and maybe a little more’?
-
-
This is the sort of thing I have that prompted my question — a trait that binds two lifetimes, with a method that returns a ref over one. It just so happens that one lifetime is fully nested inside the other in basically all my call sites, so I couldn’t see the problem
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.