Skip to content

Review DelayUs/DelayMs API and possible migrate away. #591

Description

@jordens

#590 (review)

We should try to get away from DelayUs/DelayMs at some point in the future. The API is an invitation for error: Into<u32> strips units, granularity, and context as delay_us(something.into()) looks just as good (but is wrong) if something.into::<u32>() are actually ms.
It does seem like we should leverage as much as possible from fugit.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dependenciesPull requests that update a dependency fileenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions