I don't understand Pin/Unpin in practice and all I'm doing is adding random `... + Unpin` when the compiler complains and it's just making more errors happen :(((
-
-
Replying to @zkat__
Sometimes instead of + Pin you have to add + Sized and it solves it. Forget when, and why tho. Wish I had anything that could help here, but outside of "use pin-project" and "look at async-std's source" I don't have much :(
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
this is literally all Greek to mepic.twitter.com/BG8wZtd2jl
1 reply 0 retweets 2 likes -
Replying to @zkat__
Looked at the code, looked at ur error. This seems.. odd? Can you double check the futures versions are the same? If you're passing from surf I don't believe we've release a futures 0.3.0 version yet; tomorrow. Don't have much else to go on for now without booting my laptop.
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
this isn't from surf. This is from my failed attempt at porting tar-rs to async-std: https://github.com/zkat/tar-rs/tree/zkat/async …
1 reply 0 retweets 1 like
Oh yeah I found the code before I replied, hehe. I was more trying to say that if you're testing tar/untar *with* surf then the traits won't be lining up yet, which would explain these errors. But I guess that's not the case, hmm.
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.