Skip to content

refactor: always use return await instead of return #684

@KnorpelSenf

Description

@KnorpelSenf

This will improve stack traces, but add extra spins to the event loop. We have to bench this and then decide whether to move forward with it. If this is a noticeable bottleneck (hot path of the lib) then we should prevent this from happening.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions