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
{{ message }}
This repository has been archived by the owner on Jan 30, 2021. It is now read-only.
In client, strings at arguments should be &str and those in return value should be String, and in server, vice versa.
open issue
In server, how to settle the lifetime of return value? fn foo(&self, arg: String) -> &str will inferred to fn foo<'a>(&'a str, arg: String) -> &'a str. Is this correct (usable) ?.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In client, strings at arguments should be
&str
and those in return value should beString
, and in server, vice versa.open issue
In server, how to settle the lifetime of return value?
fn foo(&self, arg: String) -> &str
will inferred tofn foo<'a>(&'a str, arg: String) -> &'a str
. Is this correct (usable) ?.The text was updated successfully, but these errors were encountered: