Skip to content

feat: plan & implement miri support #3554

Description

@scottgerring

miri is widely used in the ecosystem but not supported by us. This can cause issues - in #3523 , a user relying on otel-rust and using miri in their own application had their miri job break due to changes in otel-rust. It would be great for us to support miri, but this is quite a big lift to do meaningfully as lots of things can cause issues - for instance system calls, which we tend to wrap a lot of.

This ticket is intended to capture discussion around a plan to support miri "properly" so that we can benefit from it here, and minimise the pain downstream users of the crates may feel.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-commonArea:common issues that not related to specific pillarpriority:p3Lowest priority issues and bugs.

    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