Add fuzz subcommand

[nyonson]

Initially only supporting the dynamic listing of targets, but that might still be super helpful for the CI jobs. The command is following a similar style of integration where it is assuming some sort of fuzz crate in the workspace.

Related to #5

[tcharding]

I don't see why we have to use bitcoin-fuzz as the package name in rust-bitcoin, would it be easier (in future perhaps) to change it and use fuzz as the default here?

[nyonson]

Yea, probably. We are the only users so easy to roll out. I was just taking the path of least resistance for now.

[tcharding]

ACK 743fab9

[tcharding]

I acke'd because if it works it works. But did you try it out on rust-bitcoin? I was surprised to not see the path field handled explicitly.

E.g

[[bin]]
name = "bitcoin_arbitrary_block"
path = "fuzz_targets/bitcoin/arbitrary_block.rs"

[nyonson]

I acke'd because if it works it works. But did you try it out on rust-bitcoin? I was surprised to not see the path field handled explicitly.

Yea, I am running it on rust-bitcoin and it prints out the targets (e.g. bitcoin_arbitrary_block), is it throwing an error for you?

[tcharding]

No I didn't test this one, was lazy and just asked you. 'trust don't verify', right?

[nyonson]

2ef2083: rebased

[apoelstra]

BTW do we expect this crate to be formatted? It's pretty close to being so.

[nyonson]

BTW do we expect this crate to be formatted? It's pretty close to being so.

I am planning on adding the same lint and fmt rules as rust-bitcoin with #54

[tcharding]

ACK 2ef2083

[nyonson]

9a24e67: rebased and switched the default package name to just fuzz.

[tcharding]

ACK 9a24e67

[apoelstra]

utACK 9a24e67