Warnings when launching build about replibyte HOT 3 OPEN

This also somewhat bothered me, it does make development with a lot of re-builds a little annoying.
A very simple solution would be to add

#![allow(unused)] // TODO remove it when the code is stable

to both /src/main.rs and /dump-parser/src/lib.rs as the 1st line, and all those warnings will be gone.

from replibyte.

I opened this ticket as I'm trying to learn Rust, and would like to contribute :-)
So I can clean all these warnings in different pull requests, but I wanted to be sure if it's intended (for future features) or it's just some missing cleaning during development.

I could do some small PRs (one for each warning) and you could accept or decline, depending on the need of variables / functions. What do you think?

from replibyte.

@pascalgrimaud It's great that you want to learn Rust and contribute and I'd be happy to help with what I can 🙂
It's just that most of these warnings as you can see are only due to unused variables or structs, which will only be utilized in the future of the crate development.
So basically cleaning these warnings just means to keep developing the crate :)

from replibyte.