https://github.com/infogulch/its_ok_to_be_block_on

A minimal implementation of block_on, to execute futures in a syncronous context.
https://github.com/infogulch/its_ok_to_be_block_on

Last synced: 13 days ago
JSON representation

A minimal implementation of block_on, to execute futures in a syncronous context.

• Host: GitHub
• URL: https://github.com/infogulch/its_ok_to_be_block_on
• Owner: infogulch
• License: apache-2.0
• Created: 2024-02-06T22:06:55.000Z (9 months ago)
• Default Branch: master
• Last Pushed: 2024-02-06T22:16:24.000Z (9 months ago)
• Last Synced: 2024-10-10T22:37:48.475Z (about 1 month ago)
• Language: Rust
• Homepage:
• Size: 7.81 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE-APACHE

Awesome Lists containing this project

README

        
# It's ok to be `block_on`

Sometimes you just need `block_on`, without an entire bloated futures runtime.

It's ok.

This crate copies and exports the per-thread `block_on` implementation (and

license) from the [`futures` package](https://github.com/rust-lang/futures-rs),

minimizing the size of the code and the dependency tree, allowing users to block

on the completion of a future in a syncronous context without needing to create

and manage an executor.

## Does it work?

It compiles. ¯\\_(ツ)_/¯