Skip to content

Call stack saftey via backtrace #15

@Shizcow

Description

@Shizcow

Currently, the only unsafe portion of this crate is that trying to patch a parent function (without the unsafe force) causes a deadlock. Using the backtrace crate it may be possible to detect when this occurs and issues an error. It may be difficult to ensure that the function identities are the same, and to ensure that this does not cause a significant runtime penalty.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions