Nick Fitzgerald
Nick Fitzgerald
There is a comment about preventing including the source-map lib when in a browser build. ``` // And prevent from including source-map by browserify ``` Two things: a) the source-map...
Would be nice not to have them, or at least suppress them. I'm dealing with other things at the moment, but figured I should post this for posterity. ``` warning:...
First off: thanks for a lovely tool; I use it for a ton of my crates :) I also include `#[test]`s to make sure that the readme is up-to-date, and...
> Note: I mentioned this in a comment in #61 but I think it is worth making a top-level issue / proposal for. We want adapter functions to be able...
From the explainer: > Validating a Web IDL Bindings section primarily involves type checking all the contained binding expressions relative to the respective source and destination tuple types of the...
https://blog.rust-lang.org/inside-rust/2020/11/12/source-based-code-coverage.html I'm imagining this would run the whole corpus and then show you the coverage, or run fuzzing for N amount of time and then show you the coverage. Related:...
This would be particularly useful for folks running `cargo fuzz` in their CI, so they didn't have to wait on `cargo-fuzz` itself to build.
Steps to reproduce: ``` $ cargo new blah Created binary (application) `blah` package $ cd blah/ $ cargo fuzz init $ cargo fuzz run fuzz_target_1 -O -a Updating git repository...
This is something that hasn't been super clear to me, and I haven't really seen it discussed anywhere ever. The corpus * can end up getting sizable (see also #163)...
`libfuzzer-sys` will just build and link `libfuzzer.a`. `libfuzzer` will depend on `libfuzzer-sys` and additionally export our nice `fuzz_target!` macro. I started poking at this over in https://github.com/fitzgen/libfuzzer/tree/split-libfuzzer-and-libfuzzer-sys but quickly ran...