plotchy

drafting this bc this isn't a good solution. it inflates the corpus too much and should have logic for corpus replacement on closer comparisons.

After experimenting more I think doing this in `should_replace()` is probably better. No need for a Feedback https://github.com/fuzzland/ityfuzz/blob/2ffa214e8eb67490366ac8f27ffe81ab8196bee8/src/fuzzer.rs#L169-L188

I force pushed a new implementation. This adds a new metadata that is also checked in the `should_replace` function. It no longer inflates corpus. Now it replaces items with the...

There are some overlapping ranges in the match statements, but they are intentional. Matches don't support exclusive ranges for constants atm.

@shouc At the moment I've been testing through modifying the PowerScheduler's `next()` fn to only select from testcases that I've chosen as closest. I chose to do it this way...

[DARWIN](https://arxiv.org/pdf/2210.11783) paper has a different take on this using an evolution system. tho oddly default AFL seems to perform very closely to DARWIN and better than MOpt. Maybe this is...

I agree! When deep in a trace with many breakpoints already, stepping backwards would be very helpful over re-running and attempting to find the same spot

copying good background provided by @evalir from #5776 : > --skip-simulation avoids using the provided URL to do gas estimation. It does not prevent foundry from simulating the script locally....