Skip to content

signature: reconsider allow(async_fn_in_trait)? #2393

@tarcieri

Description

@tarcieri

I'm curious why we're suppressing this lint. The reason given in #1419 which did the original AFIT migration is:

#[allow(async_fn_in_trait)] is required until a solution to RPITIT is merged in rust.
This put responsability on the implementor of async_signature::AsyncSigner to make sure their future is Sendable.
see rust-lang/rust#115822 (comment) for more context.

RPITIT shipped in 1.75.0, so should we reconsider this?

cc @baloo

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