Skip to content

Poisonable shouldn't poison for shared locks #4

@botahamec

Description

@botahamec

According to the documentation of RwLock (emphasis mine):

An RwLock is poisoned whenever a writer panics while holding an exclusive lock.

This makes sense, since there is no possibility of putting the inner value in an invalid state when you cannot modify the inner value.

The Poisonable type currently included in HappyLock poisons for both exclusive and shared locks. This should be fixed.

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