Skip to content

Verify UnwindSafety for our types #1344

Open
Open
@Lorak-mmk

Description

@Lorak-mmk

During pre-1.0 development we did not pay any attention to this trait. and unwinding in general.
Turns out we actually should, because it may cause semver-related issue - and fixing them by just implementing the trait blindly is not very elegant and defeats the purpose of this trait.
TODO before 2.0:

  • Learn more about unwind safety
  • Verify which of our types should implement UnwindSafe / RefUnwindSafe and make it so

Related: #1287 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    API-breakingThis might introduce incompatible API changesAPI-stabilityPart of the effort to stabilize the API

    Type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions