Nick Fitzgerald

Support emitting more kinds of output

2

Right now we support: * [X] human readable text * [X] JSON but it would be great to also emit: * [ ] CSV * [ ] Graphviz Dot See...

instead of `JOB=wasm ./ci/script.sh`. * [ ] in CI * [ ] publishing to npm

Improve finding edges to data segments

6

Ok, clearly this wasm's size has a lot going on in the data section: ``` ~/twiggy $ twiggy top -n 10 ~/gutenberg-parser-rs/bindings/wasm/gutenberg_post_parser.debug.wasm Shallow Bytes │ Shallow % │ Item ───────────────┼───────────┼───────────────────────────────────────────────────────────────────────────────────...

Allow custom arbitrary methods for fields in the custom derive

5

Sometimes a field of a struct doesn't implement arbitrary and it is either impossible to do (because it is from another crate, for example) or undesired. We should support some...

Allow getting an arbitrary length with a maximum upper bound

1

Sometimes you don't want more than N things generated because, for example, it makes the fuzz target too slow and run up against libfuzzer timeouts. A solution to this is...

Enum discriminants should be taken from the end of the input string, like lengths

1

The same [rationale](https://github.com/rust-fuzz/libfuzzer-sys/blob/0c450753/libfuzzer/utils/FuzzedDataProvider.h#L92-L97) for why we take lengths from the end of the input byte string applies to discriminants: depending on the discriminant chosen, it changes which subsequent arbitrary calls...

And move the `build.rs` to that sub-crate, since it is only used for generating tests. This should help cargo better-parallelize builds of crate graphs that include `cpp_demangle`. This requires somethign...

Allow users to specify a maximum length for the demangled symbol

2

Since the demangled symbol's length can be exponential in the worst case, we should allow users to clamp it down. For example, this mangled symbol ``` __Z20lets_get_exponentialP4PairIS_IS_IS_IS_IS_IS_IS_IiiES0_ES1_ES2_ES3_ES4_ES5_ES6_E ``` Demangles into...

`_ZN7mozilla3gfx12RecordedFillC2INS0_11EventStreamEEERT_` expected: `mozilla::gfx::RecordedFill::RecordedFill(mozilla::gfx::EventStream&)` actual: `mozilla::gfx::EventStream& mozilla::gfx::RecordedFill::RecordedFill()` -------------- Similar to the `is_template` checks that exist, probably need `is_ctor_dtor` as well.

After #24, and we have some meaningful measures of performance, we should investigate improving those measures. Filing this now so that I can jot down some ideas floating in the...