rust/crates/syntax/fuzz/Cargo.toml

[package]
name = "syntax-fuzz"
version = "0.0.1"
publish = false
edition = "2021"
rust-version = "1.76"

[package.metadata]
cargo-fuzz = true

[dependencies]
syntax = { path = "..", version = "0.0.0" }
text-edit = { path = "../../text-edit", version = "0.0.0" }
libfuzzer-sys = "0.4.5"

# Prevent this from interfering with workspaces
[workspace]
members = ["."]

[[bin]]
name = "parser"
path = "fuzz_targets/parser.rs"

[[bin]]
name = "reparse"
path = "fuzz_targets/reparse.rs"

[lints]
workspace = true
Add trivial fuzzer for parser As described in #61, fuzz testing some parts of this would be ~~fun~~ helpful. So, I started with the most trivial fuzzer I could think of: Put random stuff into File::parse and see what happens. To speed things up, I also did cp src/*/.rs fuzz/corpus/parser/ in the `crates/libsyntax2/` directory (running the fuzzer once will generate the necessary directories). 2018-09-08 16:55:53 +02:00			`[package]`
Rename ra_syntax -> syntax 2020-08-12 18:26:51 +02:00			`name = "syntax-fuzz"`
Add trivial fuzzer for parser As described in #61, fuzz testing some parts of this would be ~~fun~~ helpful. So, I started with the most trivial fuzzer I could think of: Put random stuff into File::parse and see what happens. To speed things up, I also did cp src/*/.rs fuzz/corpus/parser/ in the `crates/libsyntax2/` directory (running the fuzzer once will generate the necessary directories). 2018-09-08 16:55:53 +02:00			`version = "0.0.1"`
			`publish = false`
fix(fuzz): Fixes broken Cargo.toml for fuzz tests Fixes broken Cargo.toml for fuzz tests and adds building of fuzz tests to the CI. 2023-01-23 09:07:57 -08:00			`edition = "2021"`
fix: Ignore generic arguments in intra doc link path resolution 2024-02-28 09:38:25 +01:00			`rust-version = "1.76"`
Add trivial fuzzer for parser As described in #61, fuzz testing some parts of this would be ~~fun~~ helpful. So, I started with the most trivial fuzzer I could think of: Put random stuff into File::parse and see what happens. To speed things up, I also did cp src/*/.rs fuzz/corpus/parser/ in the `crates/libsyntax2/` directory (running the fuzzer once will generate the necessary directories). 2018-09-08 16:55:53 +02:00
			`[package.metadata]`
			`cargo-fuzz = true`

Refactor parser fuzz testing 2019-03-22 02:05:12 +09:00			`[dependencies]`
Add cargo file tidy test 2021-02-03 22:01:09 +08:00			`syntax = { path = "..", version = "0.0.0" }`
fix(fuzz): Fixes broken Cargo.toml for fuzz tests Fixes broken Cargo.toml for fuzz tests and adds building of fuzz tests to the CI. 2023-01-23 09:07:57 -08:00			`text-edit = { path = "../../text-edit", version = "0.0.0" }`
			`libfuzzer-sys = "0.4.5"`
Add trivial fuzzer for parser As described in #61, fuzz testing some parts of this would be ~~fun~~ helpful. So, I started with the most trivial fuzzer I could think of: Put random stuff into File::parse and see what happens. To speed things up, I also did cp src/*/.rs fuzz/corpus/parser/ in the `crates/libsyntax2/` directory (running the fuzzer once will generate the necessary directories). 2018-09-08 16:55:53 +02:00
			`# Prevent this from interfering with workspaces`
			`[workspace]`
			`members = ["."]`

			`[[bin]]`
			`name = "parser"`
			`path = "fuzz_targets/parser.rs"`
Add fuzz test for reparsing 2019-03-22 02:06:48 +09:00
			`[[bin]]`
			`name = "reparse"`
			`path = "fuzz_targets/reparse.rs"`
Use Cargo's [workspace.lints.*] to config clippy 2023-12-29 23:22:29 +09:00
			`[lints]`
fix: Ignore generic arguments in intra doc link path resolution 2024-02-28 09:38:25 +01:00			`workspace = true`