cargo-fuzz icon indicating copy to clipboard operation
cargo-fuzz copied to clipboard

Published 20 hours ago • verified publisher icon rust-fuzz

One point oh

Open Manishearth opened this issue 7 years ago • 3 comments

Is there anything blocking 1.0? My main reasons for not 1.0-ing this earlier was that the exact mechanics were in flux (building libfuzzer, the fuzz/ dir, etc), and the CLI was uncertain.

Now we have a proper CLI that probably won't change. We don't do a special libfuzzer build anymore. The fuzz scripts are much cleaner (macros!) and while we may add quickcheck support later, I don't think that will be backwards-incompatible.

Is there anything else we need to decide, or issues that should be fixed, before going 1.0?

cc @frewsxcv @nagisa

Manishearth avatar Mar 30 '17 03:03 Manishearth

Would be nice to get this working natively on macOS. That might just need an LLVM bump, not really sure.

frewsxcv avatar Mar 30 '17 03:03 frewsxcv

I don't think that's a breaking change though

Manishearth avatar Mar 30 '17 04:03 Manishearth

Just to give my input - I don't think we have anything blocking. Most of the issues are feature requests or random bugs that shouldn't be breaking in the future.

daniellockyer avatar Mar 30 '17 05:03 daniellockyer