#async #python #markdown #ai #will-mcgugan #generative-ai #llms #textual #llm #uv
Origin | Interest | Match
SQLite async connection pool for high-performance
https://github.com/slaily/aiosqlitepool
#HackerNews #SQLite #async #connection #pool #high-performance #aiosqlitepool #database
C++ Coroutines Advanced: Converting std:future to asio:awaitable
https://www.ddhigh.com/en/2025/07/15/cpp-coroutine-future-to-awaitable/
#HackerNews #C++ #Coroutines #Advanced #std::future #asio:awaitable #programming #async #await #C++
asyncmcp – Run MCP over async transport via AWS SNS+SQS
Swift concurrency. Executors, Actors и их связь с потоками
В данной части из серии статей мы погрузимся чуть глубже в недра Swift Concurrency. Как определяется поток, на котором будет выполняться Task? Почему в рамках одной Task поток может меняться? Что такое Executor и на какие типы он делится? За что отвечает TaskExecutor, а за что SerialExecutor? Как определить текущий Executor по коду? Как использовать свой самописный Executor? В этой статье ответим на эти (и многие другие) вопросы.
To pin or to unpin, that is truly the question
What if your PHP functions could pause, resume, and remember where they left off, like little self-aware scripts?
That’s what coroutines are for, and PHP gives you two tools to use them: Generators (since 5.5) and Fibers (in PHP 8.1).
I break it all down with real code, plus a hot potato metaphor you won’t forget:
https://doeken.org/blog/coroutines-in-php?utm_source=mastodon
Willem will cover when to use Streams vs. other async patterns, how to build and chain them, and what’s going on under the hood. By the end, they’ll feel a lot less scary
2/3
JavaScript, wow!
I was under the impression that if a function returns a Promise, it never throws. Rather, in any case, it returns a Promise, rejected if the functions throws something.
But fetch() is a counter-example. Or this on the TypeScript playground:
The crucial thing is. My impression above is true for functions of the form
async f(...): Promise<...> { ... }
Just add the async in the playground to see the difference.
How I normally do #async external programs in my #commonLisp image #embeddableCommonLisp and #uiop (in the notes).
Originally I was writing Kittenette (Closette but for kittens) today, but I ended up wanting to individually treat external processes, especially from #ecl on its own first.
My example is particularly using #cat(1) as an external-process in-memory echo server.
Hope it helps someone. #programming #example
Yes "multi-processing" in the url is ~erroneous.
@noboilerplate THIS!
I think a lot of people inadvertently assume async #RustLang is so different from sync Rust, because the way it is - when in fact it's because of the (most popular) async runtime they're using.
We should look way more into alternative #async runtimes to #Tokio, e.g. smol:
https://floss.social/@janriemer/111669258656959538
#Smol allows you to use non-'static Futures by using a local executor:
https://floss.social/@janriemer/111669668856899636
It looks a lot more like "normal" #Rust.