Twitter | Pretraživanje | |
Stjepan Glavina
programmer he/they
290
Tweetovi
378
Pratim
754
Osobe koje vas prate
Tweetovi
Stjepan Glavina proslijedio/la je tweet
electrified filth 20 h
It was a lot of fun speaking with folks at FOSDEM today about sled and io_uring! Here are the slides from my talk today:
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina proslijedio/la je tweet
Kate Compton, actual doctor of weird ai 1. velj
I tell people to stop worrying about futuristic runaway smart AI, because it's stupid current AI that will kill us, this is what I mean. Someone bought a product that *literally* text-matched the word "charity" as 'good' and "vodka" as 'bad' and is making hiring choices with it.
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina proslijedio/la je tweet
caroline sinders 1. velj
A on Facebook- messenger was forcing me to change my privacy/location settings. In messenger’s unprompted pop up, I have 2 options. In iOS location services, I have 4. When I’m back in app to look for more choices, I’m taken to a mobile webpage to log into Facebook.
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina 31. sij
Odgovor korisniku/ci @chvest
I'm not sure why the futures crate is slower, but it's most likely for a silly reason like a missing #[inline] or something of that sort.
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina 31. sij
New blog post on how to build a complete async executor in Rust.
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina 25. sij
First blog post on writing your own async executors in Rust. Here's how to implement block_on() in a few lines of safe code.
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina proslijedio/la je tweet
Lisa White 23. sij
This is amazing. How it should be.
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina proslijedio/la je tweet
steveklabnik 17. sij
It's a sad day for : actix-web is dead. I am not feeling very good about our community today.
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina 16. sij
Odgovor korisniku/ci @sadisticsystems
In that scenario, wake() attempts to access the Thread instance on the stack of run(), which is dead at that moment. To fix the problem, clone() function must clone the Thread handle and forget it, and wake() and drop() must drop the Thread handle.
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina 16. sij
Odgovor korisniku/ci @sadisticsystems
I'll risk getting blocked by pointing out a potential use-after-free :) As an example, a "malicious" future could clone the Waker associated with the current thread, move it into a newly spawned a new thread, and wake it after 10 seconds, after the run() invocation completed.
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina 24. pro
Odgovor korisniku/ci @tomaka17
I published a new version of crossbeam-queue, now it works in no_std + alloc environments: crossbeam-queue = { version = "0.2.1", default-features = false, features = ["alloc"] }
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina 24. pro
Odgovor korisniku/ci @tomaka17
Is the alloc crate available in your no_std environment?
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina 5. pro
Odgovor korisniku/ci @jadbox
That is exactly what I had in mind as a better solution ;)
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina 4. pro
Wrote a blog post on why blocking inside async blocks is problematic and how to get around it. A follow-up is coming soon...
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina proslijedio/la je tweet
yosh 1. pro
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina proslijedio/la je tweet
Niko Matsakis 29. stu
First of the async interviews: and talk about Rust's Async I/O and WASM
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina proslijedio/la je tweet
Yaah 🦀 ☕ 27. stu
GNU project code of conducts be like
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina proslijedio/la je tweet
caroline sinders 22. stu
Slack, this is a BS answer. People have been asking for the block button for YEARS now. Not all workplaces are safe or recognize harassment AND lots of communities use slack! I worked at a workplace w over 200k employees and we used Slack. Blocking and muting ARE workplace tools
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina proslijedio/la je tweet
Florian Gilcher ∠(・.-)―〉 →◎ 21. stu
Reasons why we haven’t picked Slack (and other tools) for Rust: lack of sophisticated moderating and boundary setting tooling. Slack is especially hard because it is - by design - not built for open communities.
Reply Retweet Označi sa "sviđa mi se"
Stjepan Glavina proslijedio/la je tweet
Sebastian Dröge 12. stu
async-tungstenite would be more or less ready for release now and is updated to work with async-std 1.0 (but is still an optional dependency for just one function). Go ahead using it already if you need a websocket crate to work with async-std!
Reply Retweet Označi sa "sviđa mi se"