Can't find async-std feature here: https://github.com/hyperium/hyper/blob/master/Cargo.toml
do you have an example?
Either way, "can be configured" means that custom code for each runtime must be written, it is not like lets say "Futures", which can be used generically.
In Tokio 1.0 – async runtime for Rusthyperium
hyper
Rust2014–2026
hyperium / hyper
hyper
An HTTP library for Rust
40Distinct people
44Mentions
1Explicit recommenders
16.4KGitHub stars
What to know before exploring
What it is
An HTTP library for Rust
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
I've jumped on the Rust bandwagon as part of ZeroTier 2.0 (not rewriting its core, but rewriting some service stuff in Rust and considering the core eventually). I've used a…
api used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
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, 11:23:53 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 year44 dated mentions
Observed mentions: 2014-10-10 05:26:41 UTC to 2026-10-11 18:33:17 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 9 | 1 | 8 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 12 | 1 | 11 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 2 | 0 | 2 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
hyper
A protective and efficient HTTP library for all.
HTTP/1 and HTTP/2
Asynchronous design
Leading in performance
Tested and correct
Extensive production use
Client and Server APIs
Get started by looking over the guides.
"Low-level"
hyper is a relatively low-level library, meant to be a building block for
libraries and applications.
If you are looking for a convenient HTTP client, then you may wish to consider
reqwest.
If you are not sure what HTTP server to choose, then you may want to consider
axum or
warp, the latter taking a more functional
approach. Both are built on top of this library.
Contributing
To get involved, take a look at CONTRIBUTING.
If you prefer chatting, there is an active community in the Discord server.
License
hyper is provided under the MIT license. See LICENSE.
Read the full README on GitHubWhat Hacker News says
12 sources(Disclaimer: I work on Fly.io, this post is bias)
It will probably be a while. We've been evaluating Quic and the ecosystem just isn't quite ready. We opted to release UDP support instead, so apps that want Quic can do it, but we can avoid adding much extra plumbing in front of the simple HTTP apps.
Given how much AWS is investing in Rust, they'll probably ship first class support for Quic when Hyper does (same as us!): https://github.com/hyperium/hyper/issues/2078
In Application Load Balancers enables gRPC workloads with end to end HTTP/2 supportConsidering the discussion in https://github.com/hyperium/hyper/issues/2265, that seems unlikely.
In Memory safe ‘curl’ for a more secure internetWhen I saw the issue (https://github.com/hyperium/hyper/issues/2265) for adding support for a C API to Hyper I was puzzled - couldn't you just use curl for that?
As a user of software, it makes me happy to know that folks are investing in making the nuts and bolts safer and more secure.
In Memory safe ‘curl’ for a more secure internetThe latter is scheduled for the next release https://github.com/hyperium/hyper/issues/2223
In Memory safe ‘curl’ for a more secure internetI count 14: https://github.com/hyperium/hyper/blob/master/Cargo.toml#L22...
bytes, futures-core, futures-channel, futures-util, http, http-body, httpdate, httparse, h2, itoa, tracingfeatures, pin-project, tower-service, tokio, want
In Memory safe ‘curl’ for a more secure internetMore details here: https://github.com/hyperium/hyper/issues/2265#issuecomment-6...
In Memory safe ‘curl’ for a more secure internet(and the pull request under active development here: https://github.com/hyperium/hyper/pull/2278)
I see that Stenberg (bagder) is receiving funding for the work from the ISRG, but I wonder if McArthur (seanmonstar) is, too? It seems like a sizable amount of work on their part, too.
In Memory safe ‘curl’ for a more secure internetI've been holding my breath ever since I saw https://github.com/hyperium/hyper/issues/2265#issuecomment-6...
Glad to see it seems to be going well!
In Memory safe ‘curl’ for a more secure internetThat's a good idea. In my case, I wanted a static search that I could deploy next to my content. Cloudflare workers would require a (free) account, but most importantly they wouldn't work full offline. For bigger indices, that would be a great trade-off, though. If you like, you can try pushing tinysearch to a worker using wasm-pack. It's all Rust in the end, so you'd only need to add a `/search` route e.g. with hyper (https://github.com/hyperium/hyper).
If you're willing to experiment with this, don't hesitate to open a pr/issue on Github and we can add that feature.
In A tiny static full-text search engine using Rust and WebAssembly (2019)I'm not working with Rust but I just tried a quick benchmark by compiling a random project.
git clone https://github.com/hyperium/hyper
Full Build: time cargo build (1 min 42 seconds without download) (349K LOC total [0])
Recompile: time cargo build (2 seconds) (around 18k LOC)
I don't see the problem. The full build also includes all the 53 dependencies. So we are talking about a compilation speed of about 3.5k lines/s on a dual core 11" laptop from 2017 with turbo boost disabled.
I've personally worked on C++ projects where changing a single header can cause 5 minutes of compilation on an incremental build. Any slowdowns you have experienced may have been caused by a specific library or project.
[0] according to cloc ~/.cargo/registry/src/github.com-1ecc6299db9ec823/
In Translating Quake 3 into Rust