tokio-fiber

Async fibers for Rust `futures` and `tokio` using coroutines. Attempt at a `mioco` replacement.

Systems & Infrastructure

Explore on GitHub Read Hacker News discussions

2Distinct people

2Mentions

0Explicit recommenders

31GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Async fibers for Rust `futures` and `tokio` using coroutines. Attempt at a `mioco` replacement.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2017-01-08 14:56:46 UTC to 2017-01-08 16:05:26 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
Jan 8, 14:00	2017-01-08 14:00:00 UTC	2017-01-08 15:00:00 UTC	1	1
Jan 8, 15:00	2017-01-08 15:00:00 UTC	2017-01-08 16:00:00 UTC	0	0
Jan 8, 16:00	2017-01-08 16:00:00 UTC	2017-01-08 17:00:00 UTC	1	1

What Hacker News says

2 sources

GolDDranks·Jan 8, 2017

From the author of the mioco coroutine library, there is a new attempt to implement coroutines on top of tokio: https://github.com/dpc/tokio-fiber/ (still under construction, it seems)

In The Piston image library is now pure Rust

tupshin·Jan 8, 2017

I believe the idea is that tokio, because of its zero-cost abstractions will be able to be efficiently be the foundation of those styles. Check out https://github.com/dpc/tokio-fiber/ for co-routines being re-envisioned on tokio, and https://github.com/rust-lang/rfcs/issues/613 acknowledges that the actor story is still a work-in-progress. I have seen no indication that either coroutines or futures will be less ergonomic or performant due to being built on top of tokio's futures.

In The Piston image library is now pure Rust