This Month in Rust, `January 2026`

[Florob]

ToDo

• Settle for a date and location: Wednesday {2026-01-14}, 19:15 CET at C4 (default: first Wednesday each month)
• Basic Agenda (default: "This Month in Rust")
• Final invitation (deadline T - 10 days)
  • meetup
  • website
  • [community calendar]

Invitation draft

Title: Rust in {month}: {topic}

Rust Cologne is a monthly meetup dealing with everything Rust.
{short summary of topics}

(The meetup will likely be held in German but we'll switch to English if needed.)

Dear Rustacean,

you are hereby warmly invited to join the next Rust Cologne meetup. Whether you want to speed up your python code, write a web service, need interop with your C++-codebase, cross-compile for a microcontroller, write an emulator, … we've got you covered!

We commonly open up with a brief summary of noteworthy changes in the Rust ecosystem. Be it updates to the language itself, public events, its impact on other projects and languages, …

{detailed description of topics}

As usual, the remaining time is about whatever you want to talk about!

Always wanted to know why Rust is harder to learn than other popular languages or why it lacks a certain feature? When is it appropriate to rewrite a project in Rust? Is the compiler really that slow and are the binaries really that big? Do all those safety guarantees have an impact on the performance? Fetch a drink and let's find out.

You can register here.

See you soon!

Yours,
Florian and Kai

---

If you have a topic you'd like to talk about, please let us know in advance. This way we can make sure there's a time-slot for you and maybe announce it officially. Thank you.

Rust News

• Rust 1.92
  • Blog Post
  • Release Notes

[Florob]

Happy new year.
So our January meetup is coming up. And we presumably have settled on cancelation safety (and futurelock) as a topic. Examples and insights welcome.
While the 7th is not that early in the month, I'm currently assuming we'll be meeting on the 14th. @kawogi

[kawogi]

Happy new year as well!

14th is good - it'll make it easier to gather more people.

I'd expand the topic to more general pitfalls with async. Other problems include deadlocks (got a nasty one at work), silent failures, function coloring and overall increase of code complexity. We might want to touch "structured concurrency" and talk about whether async is the right solution for a given problem at all.

Another topic might be pros and cons of tokio.

[maierlars]

Happy new year! Lars here.
Julia just pointed me to this thread. I'm still up for contributing, in particular topics like futurelock (as pointed out by @Florob) If we share the work, I'm more than happy to refresh my understanding of the futurelock blog post and give a detailed explanation why the code fails.