Hacker GitHub

← All repos

tokio-rs/tokio

View on GitHub ↗ ★ 33,564 Rust

A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...

49 mentions on Hacker News by 43 people: 4 stories, 45 comments · first 2016-08-05 · latest 2026-09-14

Mentions per year 49 mentions · busiest year 2020 (10)
20082026
  1. https://github.com/tokio-rs/tokio
    comment by carllerche · 2026-09-14 · in Principles for Fast Tokio Applications
  2. …to Tokio here which suggests a lack of understanding of what the specific guarantees given are: https://github.com/tokio-rs/tokio/pull/7622 The tests do not appear to simulate the queue in Loom, which would be a very, very good idea. This…
  3. …this particular landmine. [1] https://docs.rs/tokio/latest/tokio/sync/mpsc/struct.Sender.h... [2] https://github.com/tokio-rs/tokio/pull/5947 [3] https://rfd.shared.oxide.computer/rfd/0400
    comment by sunshowers · 2025-10-03 · in Cancellations in async Rust
  4. …in the first place. But because they do, offering prebuilt artifacts is not viable at scale. [1] https://github.com/tokio-rs/tokio/blob/master/tokio/Cargo.to...
    comment by majewsky · 2025-06-14 · in Rust compiler performance
  5. > It’s also a pleasant language to work in I know, practically self-documenting code! https://github.com/tokio-rs/tokio/blob/tokio-1.45.0/examples... I'm not trying to pick on tokio, it was just a public link demonstrating that the syntax…
  6. …kills just that thread and not the whole program. And it seems that Tokio has the same behavior. https://github.com/tokio-rs/tokio/issues/2002#issuecomment-6... And web frameworks like Tower provide standard ways of handling panics and…
    comment by brokencode · 2025-02-08 · in The inevitability of the borrow checker
  7. …If wanting to do intrusive pointers into them, one risks creating overlapping references: https://github.com/tokio-rs/tokio/issues/3399
  8. …so at least I'll have something to point to assuming the status quo continues indefinitely. [1]: https://github.com/tokio-rs/tokio/blob/ee19b0ed7371b069112b9...
    comment by saghm · 2025-01-24 · in Build It Yourself
  9. …you will overflow[0] the task local queue and be bottlenecked by the global queue mutex[1] [0]: https://github.com/tokio-rs/tokio/blob/8897885425bf3d89053f8... [1]: https://github.com/tokio-rs/tokio/blob/8897885425bf3d89053f8...
  10. …eyes so hard it's actually audible. Every one of these 764 bugs compiled and passed type checks: https://github.com/tokio-rs/tokio/labels/C-bug Not picking on tokio in particular, mind you, finding and fixing bugs is a sign of quality in a…
    comment by samatman · 2024-10-25 · in Async Rust in Three Parts
  11. …It would be incredibly sad if people are still struggling with Pin long after I'm dead. [1] https://github.com/tokio-rs/tokio/blob/master/tokio-stream/s...
    comment by josephg · 2024-09-26 · in Rewriting Rust
  12. …they even weren't that far of doing so[2] [1]: https://news.ycombinator.com/item?id=36497399 [2]: https://github.com/tokio-rs/tokio/issues/1830
    comment by littlestymaar · 2023-10-06 · in Thread-per-core
  13. …most, and that's not there because of work stealing. I want scoped concurrency. Something like < https://github.com/tokio-rs/tokio/issues/2596 >. Another thing I really hate about Rust async right now is the poor instrumentation. I'm…
    comment by scottlamb · 2023-10-06 · in Thread-per-core
  14. "[W]ith "NO unsafe code...."* * except all the unsafe code in the dependencies (e.g. https://github.com/tokio-rs/tokio/search?q=unsafe )
  15. …developers must now reason about that. (random example pulled from a popular networking crate: https://github.com/tokio-rs/tokio/blob/718d6ce8cac9f2e081c0a... ) It isn't trivial to pick up from scratch, especially if one comes from a much…
  16. …would I compile + run as wasm32-wasi instead of stable-x86_64-unknown-linux-gnu? Interesting links: https://github.com/tokio-rs/tokio/issues/4827 - tokio support https://github.com/async-rs/async-std/issues/505 - async-std support…
    comment by MuffinFlavored · 2022-11-23 · in Wasmer 3.0
  17. …https://github.com/rust-lang/rust/issues/63818 [2] https://github.com/rust-lang/rust/pull/82834 [3] https://github.com/tokio-rs/tokio/pull/3654
    comment by celeritascelery · 2022-04-03 · in Lifetime Annotations for C++
  18. Tokio users: this string occurs here: https://github.com/tokio-rs/tokio/blob/b42f21ec3e212ace25331...
    comment by PeterCorless · 2022-01-21 · in Security vulnerability in Rust standard library
  19. …working on an alternative utility that should hopefully avoid the issues described here and others: https://github.com/tokio-rs/tokio/pull/4335
  20. …set a name. It's unstable at the moment so you would need to set the tokio_unstable cfg flag. [1]: https://github.com/tokio-rs/tokio/blob/master/tokio/src/task...
    comment by lkt · 2021-12-17 · in Tokio Console
  21. …it. [0]: See `atomic.Load(&netpollWaiters) > 0` in https://golang.org/src/runtime/proc.go [1]: https://github.com/tokio-rs/tokio/blob/master/tokio/src/runt... [2]: https://tokio.rs/blog/2019-10-scheduler#a-better-run-queue [3]:…
    comment by kprotty · 2021-09-13 · in Resource efficient Thread Pools with Zig
  22. …projects get to very late in their lifecycle, if they ever get to it at all. Tokio is no exception: https://github.com/tokio-rs/tokio/issues/2443 When I used to write more networking C code, I used to be careful to write my libraries to be…
  23. …with Rust coroutines (async functions). I made an attempt of implementing it for async Rust in https://github.com/tokio-rs/tokio/issues/1879 with a concrete implementation in https://github.com/tokio-rs/tokio/pull/2579 It mostly follows…
    comment by Matthias247 · 2021-06-01 · in Libdill: Structured Concurrency for C (2016)
  24. …I have seen many Rust projects and they were all filled with unwraps. Two random Rust projects: https://github.com/tokio-rs/tokio : $ grep -irn 'unwrap' | wc -l 1398 https://github.com/denoland/deno : $ grep -irn 'unwrap' | wc -l 2050 I…
    comment by johnisgood · 2021-03-22 · in How Safe Is Zig?
  25. …need some interop work. The intention is to fix that, but it's non-trivial. We'll get there. [0]: https://github.com/tokio-rs/tokio/issues/2716
    comment by ibraheemdev · 2020-12-23 · in Tokio 1.0 – async runtime for Rust
  26. …people decided transition can happen without breaking changes hence it does not block 1.0. See https://github.com/tokio-rs/tokio/issues/2716 for details.
    comment by sanxiyn · 2020-12-23 · in Tokio 1.0 – async runtime for Rust
  27. The changelog can be found here: https://github.com/tokio-rs/tokio/releases/tag/tokio-1.0.0
    comment by aliceryhl · 2020-12-23 · in Tokio 1.0 – async runtime for Rust
  28. …though I'm not sure if it would be using ringbahn or not. [0]: https://github.com/ringbahn [1]: https://github.com/tokio-rs/tokio/issues/2411
  29. Looks like it's on the roadmap: https://github.com/tokio-rs/tokio/issues/2411
  30. …prominent authors who go out of their way to reduce their dependencies by any means necessary (e.g. https://github.com/tokio-rs/tokio/pull/1324 , which is a notably extreme case).
    comment by kibwen · 2020-08-01 · in The semver trick (2019)
  31. …scheduler ( https://tokio.rs/blog/2020-04-preemption/ ), and a bunch of other new utilities ( https://github.com/tokio-rs/tokio/releases/tag/tokio-0.2.12 , https://github.com/tokio-rs/tokio/releases/tag/tokio-0.2.11 ). Standardization can…
  32. It's not particularly low priority https://github.com/tokio-rs/tokio/pull/1744 (See the last section in particular)
  33. …incompatibility (futures.rs) There's a bug for it in Tokio, but it's low priority as far as I know. https://github.com/tokio-rs/tokio/issues/1297
  34. How does this relate to Tokio [0]? Why should I choose this new library instead? [0] https://github.com/tokio-rs/tokio
  35. Thanks for your answers! From the second blog post I actually found https://github.com/tokio-rs/tokio/pull/660 which switched tokio from 1 reactor+worker threads to n reactors with work stealing.
    comment by Tarean · 2019-01-22 · in Asynchronous Programming in Rust book
  36. …. Further, the examples provided make futures/async/low-level socket work quite understandable. [1] https://github.com/tokio-rs/tokio
    comment by rayvy · 2018-11-27 · in Rust 2018 survey results
  37. …the Rust HTTP/2.0 implementation [3] is being driven by linkerd 2.0 (and sponsored by Buoyant). [1]: http://github.com/tokio-rs/tokio [2]: http://github.com/tower-rs/tower [3]: https://github.com/carllerche/h2
    comment by carllerche · 2018-09-20 · in Hands on with Linkerd 2.0
  38. https://github.com/tokio-rs/tokio A work-in-progress rearchitecting of the tokio-core crate in line with tokio-rs/tokio-rfcs#3
    comment by StreamBright · 2018-01-14 · in Rust in 2018: easier to use
  39. …like everyone is standardizing on futures and tokio: https://github.com/alexcrichton/futures-rs https://github.com/tokio-rs/tokio But it seems like you're most interested in Erlang-style actors with M:N green threads? The issue here is…
  40. while it's still in early days, keep you eye on the tokio project https://github.com/tokio-rs/tokio which looks to be the foundation for higher level activity in this area
    comment by tupshin · 2017-01-08 · in The Piston image library is now pure Rust
  41. …do you have of this? The issue is inter-library compatibility. https://github.com/tailhook/rotor https://github.com/tokio-rs/tokio Totally incompatible, even though they build on the same low level library.…
    comment by 15155 · 2016-12-22 · in Announcing Rust 1.14
  42. …channels or writing lots of ugly callback code By which [1] is meant, for those not knowing. [1] https://github.com/tokio-rs/tokio
  43. For those not aware of it, Tokio https://github.com/tokio-rs/tokio is a platform that is being built on top of Rust Futures for building exactly these types of services. It's built around futures and mio, so Tokio services are async, and…
    comment by bluejekyll · 2016-10-19 · in Ask HN: What is the state of C++ vs. Rust?
  44. Checkout https://github.com/tokio-rs/tokio . It builds on top of future-rs
    comment by alexnewman · 2016-08-12 · in Zero-cost futures in Rust
  45. …of this work: Announcement: https://medium.com/@carllerche/announcing-tokio-df6bb4ddb34 Code: https://github.com/tokio-rs/tokio I think the work is headed in a good direction. I introduced a `Service` trait similar to Finagle to make…