Carl Lerche
@carllerche.com
I do stuff, I say stuff. It's serious business.
I went on a podcast to talk about Rust, async programming, and Tokio. Happy to answer any questions or you can just tell me I'm wrong.
hubs.ly/Q040QsRg0
hubs.ly/Q040QsRg0
High Leverage | Ep. #6, Async Runtime For Rust with Carl Lerche of Tokio | Heavybit
On episode 6 of High Leverage, Joe Ruscio speaks with Carl Lerche of Tokio about building high-performance systems in Rust.
hubs.ly
February 4, 2026 at 6:06 PM
I went on a podcast to talk about Rust, async programming, and Tokio. Happy to answer any questions or you can just tell me I'm wrong.
hubs.ly/Q040QsRg0
hubs.ly/Q040QsRg0
Reposted by Carl Lerche
We’re excited to share the complete list of speakers joining us at TokioConf 2026 covering performance tricks, architecture patterns, and more.
See all our speakers: www.tokioconf.com/speakers
(Schedule coming soon)
Tickets are on sale: www.eventbrite.com/e/tokioconf-...
See all our speakers: www.tokioconf.com/speakers
(Schedule coming soon)
Tickets are on sale: www.eventbrite.com/e/tokioconf-...
Meet the Speakers — TokioConf 2026
Discover the speakers behind TokioConf 2026. From core maintainers to community leaders, our lineup shares real-world experience and insights.
www.tokioconf.com
January 9, 2026 at 10:11 PM
We’re excited to share the complete list of speakers joining us at TokioConf 2026 covering performance tricks, architecture patterns, and more.
See all our speakers: www.tokioconf.com/speakers
(Schedule coming soon)
Tickets are on sale: www.eventbrite.com/e/tokioconf-...
See all our speakers: www.tokioconf.com/speakers
(Schedule coming soon)
Tickets are on sale: www.eventbrite.com/e/tokioconf-...
Buy your ticket now! If we sell out soon, we might be able to expand to accommodate more, but only if we have enough time to do so!
January 8, 2026 at 11:49 PM
Buy your ticket now! If we sell out soon, we might be able to expand to accommodate more, but only if we have enough time to do so!
The #tokioconf speakers and talks just got posted: www.tokioconf.com Ticket sales are open! Since it is our first conference, it is hard to estimate how many people will come. We're starting conservative, only 200 tickets right now.
TokioConf 2026 | Be a Part of Tokio's Official Conference!
Join 300+ developers at the inaugural TokioConf 2026 to exchange ideas, learn from one another, and explore the future of async Rust. Hosted by the Tokio Project
www.tokioconf.com
January 8, 2026 at 11:48 PM
The #tokioconf speakers and talks just got posted: www.tokioconf.com Ticket sales are open! Since it is our first conference, it is hard to estimate how many people will come. We're starting conservative, only 200 tickets right now.
Reposted by Carl Lerche
For Rust people interested in async code at TokioConf, I'll see y'all in April!
January 5, 2026 at 5:56 PM
For Rust people interested in async code at TokioConf, I'll see y'all in April!
Maybe `clone_handle()` is enough to disambiguate. Though, it isn't short.
October 15, 2025 at 3:13 PM
Maybe `clone_handle()` is enough to disambiguate. Though, it isn't short.
You may not have a problem with it, but it is something I see *many* software engineers working with Rust have problems with. Consider the type being cloned may not be Vec or Arc but some custom type. Being able to understand the execution behavior of code in a localized context is pretty important.
October 15, 2025 at 3:12 PM
You may not have a problem with it, but it is something I see *many* software engineers working with Rust have problems with. Consider the type being cloned may not be Vec or Arc but some custom type. Being able to understand the execution behavior of code in a localized context is pretty important.
I’ve been of the belief that using clone as the main api for incrementing ref counts is not great beyond the boilerplate of cloning: it hides the complexity of the op when looking at some code in isolation. The good news is that this can be fixed in a backwards compatible way.
October 7, 2025 at 5:46 PM
I’ve been of the belief that using clone as the main api for incrementing ref counts is not great beyond the boilerplate of cloning: it hides the complexity of the op when looking at some code in isolation. The good news is that this can be fixed in a backwards compatible way.
I do agree that there is a concept of Handle already across the rust ecosystem and nailing down a trait to represent that is good. Not sure if Handle is idiomatic as rust traits with one method tend to be verbs. It would also cause some clash with existing types names Handle. Minor issues though.
I think "handle" is the right name here, I actually came up with it independently but didn't want to wade into the discourse about it smallcultfollowing.com/babysteps/bl...
The Handle trait · baby steps
smallcultfollowing.com
October 7, 2025 at 5:42 PM
I do agree that there is a concept of Handle already across the rust ecosystem and nailing down a trait to represent that is good. Not sure if Handle is idiomatic as rust traits with one method tend to be verbs. It would also cause some clash with existing types names Handle. Minor issues though.