Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore: handle std Mutex poisoning in a shim #2872

Merged
merged 4 commits into from
Sep 25, 2020
Merged

chore: handle std Mutex poisoning in a shim #2872

merged 4 commits into from
Sep 25, 2020

Commits on Sep 25, 2020

  1. chore: handle std Mutex poisoning in a shim 

    As tokio does not rely on poisoning, we can
avoid always unwrapping when locking by handling
the `PoisonError` in the Mutex shim.

Signed-off-by: Zahari Dichev <zaharidichev@gmail.com>
    @zaharidichev
    zaharidichev committed Sep 25, 2020
    Configuration menu
    Copy the full SHA
    49039ff View commit details
    Browse the repository at this point in the history

  2. Fix fmt 

    Signed-off-by: Zahari Dichev <zaharidichev@gmail.com>
    @zaharidichev
    zaharidichev committed Sep 25, 2020
    Configuration menu
    Copy the full SHA
    7a0f0da View commit details
    Browse the repository at this point in the history

  3. Fix unsused code error 

    Signed-off-by: Zahari Dichev <zaharidichev@gmail.com>
    @zaharidichev
    zaharidichev committed Sep 25, 2020
    Configuration menu
    Copy the full SHA
    d408329 View commit details
    Browse the repository at this point in the history

  4. Add wrapper around the loom Mutex 

    Signed-off-by: Zahari Dichev <zaharidichev@gmail.com>
    @zaharidichev
    zaharidichev committed Sep 25, 2020
    Configuration menu
    Copy the full SHA
    7981985 View commit details
    Browse the repository at this point in the history