Joe Ranweiler
Joe Ranweiler
@asomers, any thoughts on how we can help out moving forward?
Hi! FYI, I'm currently looking into this, and starting a conversation with my former coworkers about the state of Rust verification via SAW/Cryptol.
Hmm, yeah, I agree that is a useful correspondence for e.g. grepping around the codebase. On the other hand, as a library user, I don't think I benefit much from...
Note that this also occurs in `common.py` in the `DeepState::api_log_stream()` method.
See this commit, and keep in mind when addressing #48: https://github.com/trailofbits/deepstate/commit/a81f816d89182e49aeba1a9ada4651d662f33871
Since this crate has been flagged as unmaintained by RustSec, depending on it will fail builds for `cargo audit` CI users. There has been some forking already, but AFAICT, it...
Thanks, @djc and @RazrFalcon. As a courtesy, I'd like to give this crate's maintainer(s) time to respond. That said, IMO it's important for the community to have a nice wrapper...
Understood, thanks for the update @BurntSushi!
This is now largely addressed. We should still improve the API around possible misuse of `Bencher::run()` (e.g. calling it outside of a benchmark function).
Now that we have `LineReporter`, others should probably live in their own crates.