Lib.rs

› waker-fn › Reviews

These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.

The current version of waker-fn is 1.1.1.

cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.

safe-to-run

This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…

unknown

May have been packaged automatically without a review

These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.

The current version of waker-fn is 1.1.1.

1.1.0 (older version) Rating: Positive Thoroughness: High Understanding: High

by MaulingMonkey on 2020-09-06

Basic 0-dependencies Fn-based Waker source.

This could eventually be made safe when Wake (not Waker!) stabilizes. In the meantime, this crate manually creates a Waker via RawWaker. This requires some unsafe code, but this crate appropriately uses just about the bare minimum necessary to accomplish the task, and appears to do so soundly and correctly. Additionally, the code is minimal (63 LOC including comments and whitespace for 1.1.0) and straightforward.

Full Audit

1.0.0 (older version) Rating: Positive Thoroughness: High Understanding: High

by MaulingMonkey on 2020-09-06

Show review…

Basic 0-dependencies Fn-based Waker source.

This could eventually be made safe when Wake (not Waker!) stabilizes. In the meantime, this crate manually creates a Waker via RawWaker. This requires some unsafe code, but this crate appropriately uses just about the bare minimum necessary to accomplish the task, and appears to do so soundly and correctly. Additionally, the code is minimal (63 LOC including comments and whitespace for 1.1.0) and straightforward.

Full Audit

Lib.rs has been able to verify that all files in the crate's tarball are in the crate's repository with a git tag matching the version. Please note that this check is still in beta, and absence of this confirmation does not mean that the files don't match.

Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories, so there is a possibility that published crates have a misleading repository URL, or contain different code from the code in the repository.

To review the actual code of the crate, it's best to use cargo crev open waker-fn. Alternatively, you can download the tarball of waker-fn v1.1.1 or view the source online.