#Async

2025-06-17

How I normally do #async external programs in my #commonLisp image #embeddableCommonLisp and #uiop (in the notes).

screwlisp.small-web.org/progra

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.

Jan :rust: :ferris:janriemer@floss.social
2025-06-14

@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:

floss.social/@janriemer/111669

#Smol allows you to use non-'static Futures by using a local executor:

floss.social/@janriemer/111669

It looks a lot more like "normal" #Rust.

#RustAsync #AsyncRust #Concurrency

SelAromDotNetselaromdotnet
2025-06-12

Need to timeout an await in c#? Ensuring your tasks complete or fail gracefully is crucial, and whether you use the newer built in framework features or need to build one yourself, this post shows you how to do it! link.content360.io/xmeuex0

2025-06-12

C++OnSea 2025 SESSION ANNOUNCEMENT: Extending std::execution Further: Higher-Order Senders and the Shape of Asynchronous Programs by Robert Leahy

cpponsea.uk/2025/session/exten

Register now at cpponsea.uk/tickets/

#async #asynchronous #cplusplus #cpp

N-gated Hacker Newsngate
2025-06-10

Oh look, another library to help you scrape the like a pro... or at least until every CAPTCHA on the planet realizes you're a 🐍 faking it. 😅 Because, clearly, the world needed an "async" way to prove that you’re not a human. 🤖💻
github.com/autoscrape-labs/pyd

Hacker Newsh4ckernews
2025-06-10
2025-06-06

A simple #embedded #Rust project running on the Raspberry Pi #Pico (#RP2040), built with #Embassy #async framework and no_std runtime complete with basic #ReverseEngineering of how it works under the hood. github.com/mytechnotalent/rust

2025-06-06

Triggered by my current swearing about async infestation everywhere I thought I'd point to this old blog entry again to remind me that I am not the only one.

journal.stuffwithstuff.com/201

#javascript #async #asyncisapest

𝕂𝚞𝚋𝚒𝚔ℙ𝚒𝚡𝚎𝚕kubikpixel@chaos.social
2025-06-05

Async Rust: When to Use It and When to Avoid It

“Asynchronous” (often abbreviated as “async”) is a widely used term in computer science, but its meaning varies depending on the context. […]

🦀 fmoya.dev/posts/async-rust/

#rust #rustlang #async #code #depense #dev #coding #development #it #rustdev

TechKeysXTechKeysX
2025-06-03

Async to run background function or task and return a value in C# Tip #41 To run a background task with async, define an async function that returns a value (e.g. string, int). Use await to get the result, matching types.

Felix Palmen :freebsd: :c64:zirias@bsd.cafe
2025-06-03

Solved! 🥳

This was a pretty "interesting" bug. Remember when I invented a way to implement #async / #await in #C, for jobs running on a threadpool. Back then I said it only works when completion of the task resumes execution on the *same* pool thread.

Trying to improve overall performance, I found the complex logic to identify the thread job to put on a pool thread a real deal-breaker. Just having one single MPMC queue with a single semaphore for all pool threads to wait on is a lot more efficient. But then, a job continued after an awaited task will resume on a "random" thread.

It theoretically works by making sure to restore the CORRECT context (the original one of the pool thread) every time after executing a job, whether partially (up to the next await) or completely.

Only it didn't, at least here on #FreeBSD, and I finally understood the reason for this was that I was using #TLS (thread-local storage) to find the context to restore.

Well, most architectures store a pointer to the current thread metadata in a register. #POSIX user #context #switching saves and restores registers. I found a source claiming that the #Linux (#glibc) implementation explicitly does NOT include the register holding a thread pointer. Obviously, #FreeBSD's implementation DOES include it. POSIX doesn't have to say anything about that.

In short, avoiding TLS accesses when running with a custom context solved the crash. 🤯

/brúno antúnɛs/sardaukar
2025-06-02
2025-05-24

#rust #rustlang #async I decided to try to adapt tower middleware to the Reqwest HTTP client. I wrote about happened. (unwoundstack.com/blog/rust-cli)

2025-05-23
2025-05-22

#rust #async from scratch 3 is now live, this time tackling pinning: natkr.com/2025-05-22-async-fro

2025-05-22

C++OnSea 2025 SESSION ANNOUNCEMENT: Extending std::execution Further: Higher-Order Senders and the Shape of Asynchronous Programs by Robert Leahy

cpponsea.uk/2025/session/exten

Register now at cpponsea.uk/tickets/

#async #asynchronous #cplusplus #cpp

Viktor Peterssonvpetersson@hachyderm.io
2025-05-21

Remote work isn’t a universal fit.

Some people thrive in solitude and structure. Others need the energy of an office.

You can’t train self-discipline--but you can hire for it.

#remotework #async #startup

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst