Twitter | Pretraživanje | |
Mike Khirallah
Lead Software Engineer
104
Tweetovi
24
Pratim
16
Osobe koje vas prate
Tweetovi
Mike Khirallah 30. sij
Odgovor korisniku/ci @yoshuawuyts @rustlang
Really reallyyyyy looking forward to websockets in tide! Can’t wait!
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 29. sij
Odgovor korisniku/ci @yoshuawuyts @asyncrs @stjepang
Thanks I will definitely follow 😊 still wish I could make a full time thing, in the mean time I’ll just keep enjoying encorporating it into my side projects....and I’ll keep reading what you push out!
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah proslijedio/la je tweet
yosh 29. sij
Working on something new.
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 29. sij
Odgovor korisniku/ci @yoshuawuyts @asyncrs
I appreciate the work you’re doing ! Really awesome. The blog is great too. I just read through your channel source code in since I was looking to use it in a stream->channels->stream pattern that I thought up and really enjoyed it. Keep up the great work!
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 29. sij
Odgovor korisniku/ci @MKrallaPro
Me: (literally talking to the compiler) “Hah! Did you see how I solved that unpinned future type issue you thought you were going to complain about? Box::pin’ed it before you could tell me otherwise!” The compiler: “ “ so sad...but so so fun 😂
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 29. sij
Although I won’t be working with in my day job any time soon, I am slightly addicted to the game where you try to prove the borrower checker that you know what you are doing on the first try 😂 I seriously get a rush from it 🤷‍♂️😆....
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 24. sij
Odgovor korisniku/ci @schusterfredl @rustlang
No one is using tide and async juniper? Must just be me I guess 😔
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 22. sij
Odgovor korisniku/ci @papertigerss @asyncrs
Really clean! I especially like the simplicity of your async fn pipe. When I was building an ext. for async bufreader in I felt like there was still a lot of friction extending functionality using futures/async. Maybe mine was just a uniq case
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 18. sij
Odgovor korisniku/ci @isosteph
This is such an accurate sentiment. Glad someone else feels this way.
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 14. sij
Odgovor korisniku/ci @asyncrs
This is awesome....anddd now I feel obligated to get async-std running on some of my esp32 devices. 😂
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 8. sij
Odgovor korisniku/ci @David_Rudnick
Hopefully this will brighten your day 😊
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 2. sij
Odgovor korisniku/ci @szeleitamas @rustlang
This made me laugh😂 thanks!
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 22. pro
So excited to have released my first crate this morning! The goal of the crate was to add additional functionality to the async BufReader implementation provided by the async-std lib . Here it is! crate: github:
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 18. pro
Odgovor korisniku/ci @asyncrs
I linked to the gist in the first post of this thread, but for reference:
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 17. pro
Odgovor korisniku/ci @asyncrs
Maybe can help? I just need a little bit of a more complex example than in the docs.
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 17. pro
Odgovor korisniku/ci @MKrallaPro
I’ve looked at how map, filter, etc is implemented under the hood but seems super complex, I want to make sure I’m doing this right
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 17. pro
Odgovor korisniku/ci @rustlang
I'm also getting an error I do not know how to resolve regarding "type annotations required: cannot resolve `TakeChunkUntil<'_, ....>` , can any experts help point me in the right direction?
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 17. pro
I'm trying to transform a BufReader into a Stream by impl'ing Stream and incrementally reading the buffer in calls to poll_next, but poll_next does not support async, so I'm stumped as to what the correct pattern is
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 16. pro
Odgovor korisniku/ci @asyncrs @rustlang @golang
This is so epic, like it’s sad how excited I got when I saw this 😂🎉
Reply Retweet Označi sa "sviđa mi se"
Mike Khirallah 11. pro
Odgovor korisniku/ci @kixunil @rustlang
Demonstrate example 2 and 3 of the following .... the ability to return a closure without allocating on the heap is extremely flexible and powerful from a functional programming standpoint.
Reply Retweet Označi sa "sviđa mi se"