@_wusher I just wrote a SO answer that might help with “such as what a lifetime bound tells the compiler” - http://is.gd/uFBM0A
-
-
Replying to @JakeGoulding
@JakeGoulding That helps a lot! One's for the reference and the other's the lifetime of the trait, so should they be different lifetimes?1 reply 0 retweets 0 likes -
Replying to @JakeGoulding
@JakeGoulding Sounds good, from SO it looks like I'll only need + 'static since the underlying types are structs1 reply 0 retweets 0 likes -
Replying to @JakeGoulding
@JakeGoulding Yea, from http://stackoverflow.com/questions/26212397/rust-lang-references-to-traits-in-structs/26213294#26213294 … + 'static constrains the underlying type to structs or &'static references1 reply 0 retweets 0 likes -
Replying to @_wusher
@JakeGoulding misread your last tweet, not sure about whether the structs can have non-static references, I'll run into it on meshes though1 reply 0 retweets 0 likes -
Replying to @_wusher
@JakeGoulding After a quick test, structs with references don't work: http://is.gd/v72ugA since the reference doesn't live long enough1 reply 0 retweets 0 likes
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.