I ran into the same issue not so long ago and at least for no_std I had to resort to using the async_trait crate. (The project is no_std but has alloc)

I can’t recall the exact error so it might have been due to mixing async and non-async methods in the same trait. I would have to look at it again…

I have never used them but there are some tools that advertise being able to run GitHub Actions locally, like WRKFLW.

I assume you mean AVIF? Because AV1 is not an image (file) format but a video compression format (that needs to be wrapped in container file formats to be storable).

The std::offload project is kinda cool. Hadn’t heard about that before.

It’ll be interesting to see where that leads.

I was under the impression that the compiler already optimizes out a lot of clones where the clone is primarily used to satisfy the borrow checker. Is that not the case?

As long as people are using Rust, it will necessarily attract this kind of action. This won’t be the last attack we will see.

I think the team has handled it quite well.

The post text doesn’t seem to get displayed on some clients (Voyager) so I’ll attach it here as well:

asciinema (aka asciinema CLI or asciinema recorder) is a command-line tool for recording and live streaming terminal sessions.

This is a complete rewrite of asciinema in Rust, upgrading the recording file format, introducing terminal live streaming, and bringing numerous improvements across the board.

There are even little interactive tools for it like: cargo-wizard

Good move. Especially for incremental builds linking tends to take up quite a large percentage of the compile time.

I’ve mostly switched to mold for that reason but having a fast default linker is nice.