Skip to content

List functions or lines that can panic #26

@alexchandel

Description

@alexchandel

(Imported from geiger-rs/cargo-geiger#50 for want of a call-stack graph).

Panics are very overused in libraries, and can unexpectedly crash unwary users and poison their mutexes. We need something to warn unsuspecting consumers which of their functions is most "explosive" / invokes the most panics, and which libraries are the cause. Without this, it's impossible for large codebases to be certain their threads won't panic and explode, nor even for small codebases that use complex libraries with many dependencies to be certain how explosive their calls truly are.

Ideally, panics provably unreachable by the compiler should not be reported. And a flag to suppress slicing panics is worthy of consideration.

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