Matthieu Pizenberg
Matthieu Pizenberg
Starting a new approach in #33
Basic implementation done in #33
Reopening since the behavior when fuzz testing is not the best. It reports logs of all the fuzz iterations whereas a much more useful behavior would be to only report...
We used to pull tree-sitter but we're not anymore. It contains C++ code and was impossible to compile with musl unfortunately despite quite some energy spent by Harry trying. So...
Having a single binary for linux is something dear to me. I'm too often annoyed by projects compiled in ubuntu and not working on arch or the reverse.
Also related to that issue is the usage of labels to match tests results and tests detection inside VSCode client plugin. I need to have a look at that (this...
Indeed, the logs are only displayed in the case of a failure. The code for the reporters lives in another repo, it is Elm code. Here is the line that...
Oh I have done an almost complete analysis for this, it is written in French for now but eventually I wanted to translate it in english, though don't have time...
@Shnatsel ok, I'll update the example repo with exact instructions to reproduce behavior in coming days.
I have updated the associated repository (https://github.com/mpizenberg/wasm-inflate) with instructions in the readme to reproduce this benchmark. Versions have changed since last April. On my computer, with rustc 1.36.0, inflate 0.4.5,...