It's hard to keep up momentum on my rust-y stuff. I write some fast as heck parser then it comes time to do the tokio/futures bit and I just hate fighting the types to get my stream-y stuff working. So hard. #rustlang
-
Show this thread
-
I've been working with the aweseom rusoto lib and the lib is great, love the work, but understanding how to integrate their tokio loop instance with my own tokio loop instance, or understanding how everything fits together is rough.
1 reply 0 retweets 1 likeShow this thread -
Then we get down to how to spawn the darn jobs. I'm always confused by between rt::run and rt::spawn. Getting the types to work is rough, I'm almost running cargo check after every few characters.
1 reply 0 retweets 1 likeShow this thread -
When I end up spawning a stream with spawn I have to handle all the possible error return values because a spawn is essentially always Result<(),()> so it's a lot of map/map_err to turn in to those values. Such a hard lesson to learn.
1 reply 0 retweets 1 likeShow this thread -
I also have no idea how to write my own streams, I want something which does buffering of individual futures/values and then chunks the results, but just combining the buffering with the timer behavior is rocket science.
1 reply 0 retweets 1 likeShow this thread -
I definitely feel like an under qualified frontiers person. Yet another wagon the trail west. Fighting the types, fighting my understanding, awash in doubts about how to make something even approaching maintainable for the next person.
1 reply 0 retweets 3 likesShow this thread -
-
Replying to @rustlang @uint128_t
We do have a lot of doc work to do though!
1 reply 0 retweets 0 likes -
Replying to @rustlang
Where can I follow the story? https://github.com/rust-lang/rust/issues/50547 …? I know async/await has a macro version now, somehwere, but maybe it'll become part of rust2018? Then there's the bit about futures 0.2 becomes futures-preview... or something!
1 reply 0 retweets 0 likes
It’s a bit tough right now! That is the tracking issue. The macro version was an experiment; the syntax has landed in nightly but needs more work.
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.