fuzzcheck-rs VS uivonim

Agreed. A while back I played around with fuzzcheck [1], which let's you write coverage-guided, structure-aware property tests, but the generation is smarter than just slamming a fuzzer's `&[u8]` input into `Arbitrary`. It also supports shrinking, which is nice. Don't know that I would recommend it though. It seemed difficult to write your own `Mutator`s. It also looks somewhat unmaintained nowadays, but I think the direction is worth exploring.

[1]: https://github.com/loiclec/fuzzcheck-rs/

Fuzzcheck is a structure-aware fuzzer for rust. "Fuzzing" means feeding large amounts of data into a program and checking for crashes (Fuzzcheck also checks to make sure that all the properties your program should uphold – e.g. a sorting algorithm applied to a list of n items should always return a list of n items – are upheld). Fuzzcheck is an "evolutionary" fuzzer – this means that it generates a set of random inputs, sees what percentage of the program is executed for each input, and keeps inputs which have high levels of percentage of program executed. It then "mutates" these inputs – whereas fuzzers such as AFL/Hongfuzz/etc mutate raw bytes in place (e.g. they swap bytes at different positions, or insert a random byte at a given position to generate inputs similar to the chosen "high coverage" inputs), Fuzzcheck works directly on the Rust types (so it might swap the order of two items in a vec, or randomly insert a new item). It's a really powerful tool for finding lots of bugs.

If you want help with Win support (issues/8) maybe post it here to get it added to TWIR.

I am working on a code coverage viewer for my fuzzer (fuzzcheck). I described what I've done so far in this issue and I am hoping to release the first version within two weeks.

The implications for my fuzzer, fuzzcheck, are huge! Compiling fuzz tests is a lot easier. There should be no more need to create a separate fuzz folder, fuzz tests can be regular #[test] functions, private implementation details can be fuzz-tested as well, rust-analyser works as expected, documentation can be easily generated, etc. I can also attach a human-readable coverage report to every test case :)

Since I graduated, I have had a lot more time to work on fuzzcheck. I am trying to flesh it out, test it, and document it for a new release. It has always felt a bit rushed/experimental and now I am hoping to make it into something solid. I have also played with an egui interface for it, to visualise the tested code coverage, understand how the fuzzer’s decisions are made, and also to interactively tweak the fuzzer’s behaviour. It's a lot of work but it's slowly all coming together! :)

fuzzcheck-rs is really cool. It combines property-testing with fuzzing, getting the nice, structured nature of the former, and the coverage-driven search of the latter, but it works by mutating the structure directly instead of going through a bit string. So if you have a binary tree, going from A(B, C) to A(C, B) can be a single mutation away if that makes sense in your use case, instead of being arbitrarily far away in the bitstring approach.

I’ve never used Redux, just haven’t cared to look into it for any projects I’ve worked on, but from a quick glance at an example it seems like it could be useful/convenient. Although then again you can write an event dispatcher in like 30 lines of TS, probably with redux-like state with a little extra work, although I’ve never tried, and that could be a bad idea in practice idk.

Instead, Nvim provides an RPC protocol that may be implemented by external GUIs. For example, there exists a plugin that embeds Nvim into Firefox when editing textboxes, GUIs that leverage Nvim's multigrid support to support smooth scrolling, translucent popups, minimaps, etc. such as Uivonim, Goneovim and Neovide, and more.

Porting my (forked, so not all my work) text editor uivonim to use Tauri instead of Electron. PR for those curious is here: https://github.com/smolck/uivonim/pull/336

Of course, I'm biased, since I work on a GUI frontend to neovim written in electron (that I forked from a project that already used electron), but I have found that it's not as bad as people make it out to be, or at least that it doesn't have to be that bad. I would like to get rid of it though if I can, maybe by doing the rendering with wgpu-rs and GUI things with egui.

I came up with this idea one day as something I could add to uivonim and the result was kinda cool; just thought I'd clean it up a bit and share. Not sure if I'll ever end up adding this for-real, but it's at least a little fun to play with ;)