Twitter | Pretraživanje | |
Lucio Franco
All day Rust type of person. Building and ! he/him
757
Tweetovi
306
Pratim
516
Osobe koje vas prate
Tweetovi
Lucio Franco 31. sij
Odgovor korisniku/ci @Pothulapati @tokio_rs
Thanks! Yes, we plan on support io_uring for sure! There are still some details to figure out but progress is being made :)
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco proslijedio/la je tweet
Vector.dev 31. sij
We've built an open source tool to help you harness, connect, transform, and route your event streams! That means your piles of logs can be collected, split, carved up, merged again, and then fed downstream! Interested?
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco 31. sij
I am super excited for io_uring and cool to see mentioned :) The future of async io is exciting!
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco 31. sij
Odgovor korisniku/ci @a_hoverbear @timberdotio
Excited to have you on the team! Looking forward to working together!
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco proslijedio/la je tweet
Maksym Zavershynskyi 30. sij
If anyone is interested in being paid for contributing to under guidance of please write me. Experience contributing to Rust concurrency projects is desirable.
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco proslijedio/la je tweet
Ivan Prisyazhnyy 30. sij
Epic sentencing - everything is strict serializable, but locks are fundamentally flawed (insafe)
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco 30. sij
Odgovor korisniku/ci @mat4nier @judsonlester
Here is an example that will not compile:
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco 30. sij
Odgovor korisniku/ci @mat4nier @judsonlester
Basically, if you have a fn on a trait that does this `bar<T>(t: T)` then it is no longer object safe, aka you can't turn it into a trait object. This is because the generic is not known at compile time and thus there is no way to know that type at compile time.
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco 30. sij
Odgovor korisniku/ci @yoeight
I played it on my friends rig, I think he has the regular 2080, since this is a more modern engine its way more optimized than any other FS sim. P3D/FSX are both built on a codebase from 2004 the ESP platform. So you can only do some much with that.
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco 30. sij
Odgovor korisniku/ci @yoeight
I have played it, its great! Im super excited :)
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco 30. sij
Odgovor korisniku/ci @judsonlester
So conclusion is: Use AT until you really need things to be generic over per trait impl, then use generics on the trait. If those don't fit use generic on a trait fn.
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco 30. sij
Odgovor korisniku/ci @judsonlester
The cost of AT vs Generic on the trait really depends but generally also comes down to how you use the trait. AT can "hide" some specific type within the trait which is _not_ generic to that trait implementation. Generics are more ergonomically costly than AT but are more flexy.
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco 30. sij
Odgovor korisniku/ci @judsonlester
Associated types when I need "some" generic type. Generic on the trait for when a method on that trait is generic over a single type in its parameters. And I rarely use generics on fn since that is not object safe but it can be useful if you have a specific situation for them.
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco 29. sij
Really lovely article talking about the "suspended coffee" culture in Naples. Through tough times you gotta stick together :)
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco 29. sij
Odgovor korisniku/ci @AriVanider @yaahc_ i 3 ostali
@ here and everyone for me is basically a short cut to "leave this server"
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco 29. sij
Odgovor korisniku/ci @yaahc_ @logicsoup @AriVanider
Mute and folders are my best friends!
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco 29. sij
Odgovor korisniku/ci @CecileTonglet
I wonder if this is a usecase for sccache?
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco 28. sij
I love serde and all the neat little hacks you can find to get what you want done. In our case we needed to encode json to check its size but then nest that within another json object. In comes RawValue and its EXACTLY what we need!
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco 28. sij
Odgovor korisniku/ci @bodil
This looks great! I was wondering if this code was public at all? I'd love to have a peek :)
Reply Retweet Označi sa "sviđa mi se"
Lucio Franco proslijedio/la je tweet
Tokio 26. sij
Trying async/await is easy with the Rust Playground:
Reply Retweet Označi sa "sviđa mi se"