Is there a way in Rust to use standard lib traits (Ord, Eq, Into/From...) with async functions?
Perhaps a crate or something?
Or must it be a separate function implemented for the structs?
I am reading the rust for rustaceans book, but it’s not the end of all, I need to implement my learning. What could be the best, short and crisp way to utilise most of async and concurrent feature in a small application?
My goal is to get confident enough that I can build/contribute to something like #pingora or a database like #quadrant
For @made and others who might have questions about the new https://thi.ng/transducers-async library, I've tried to illuminate the behind-the-scenes approach over here:
Upcoming, a new & simplified implementation of https://thi.ng/csp (currently still only on a feature branch[2]) for building blocks for Communicating Sequential Processes.
Also still WIP only, async iterable support for https://thi.ng/rdom, i.e. in the same way as rstream subscriptions, such async iterables can soon be directly embedded as component/element bodies or attribute values and then perform pinpointed DOM updates each time their value changes...
As I said, async all the thi.ngs...
[1] h/t @sjb3d for an ancient tweet with a similar sentiment & outcome :)
[2] The CSP package too was somewhat deprecated (for similar reasons) and a while ago I added another alternative CSP implementation via https://thi.ng/fibers, but that package too might see some more refactoring/simplifying by switching to async generators...
🧶 Why choose async/await over threads? - notgull.net
「 Smart programmers try to avoid complexity. So, they see the extra complexity in async/await and question why it is needed. This question is especially pertinent when considering that a reasonable alternative exists in OS threads 」
#Swift can be so much cleaner and more concise than #ObjectiveC. Really digging the new concurrency syntax with #ASync and #await for working with #CloudKit. Now if only I could convert my entire project to this. But 16 years of development has lots of legacy code. But I am slowly modernizing some of it and writing new stuff in Swift and SwiftUI.
In our latest development team working agreement someone added the item "If you're going to #Slack someone a question, don't write 'hi' and then wait for them respond, just send the question." Friends, I never felt more seen than in that very moment. #Agile#Async#Software
"io_uring is a new asynchronous I/O API for Linux created by Jens Axboe [...]. It aims at providing an API without the limitations of the current select(2), poll(2), epoll(7) or aio(7) family of system calls [...]."
Using #RevoltPHP for one of my new projects. It's very nice working with #PhpFibers and not dealing with generators/promises as much. Can't wait for other #Async#Frameworks to start refactoring to use it more. I know #AmpPhp has added it to their HttpServer lib already.