Skip to content

Add the ability to use futures_lite::future::block_on instead of async_io::block_on #2

Description

@notgull

For async programs that aren't I/O bound, they might prefer to use the non-reactor block_on and save dependencies/complexity.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions