Note for contributor @mrauhu:
I know that we spoke about this issue already a couple of times, so I reached out to a few other devs to ask their opinion about how much/if any output text should be produced by the library. There was a pretty strong preference for not having any output at all. I thought about this for a little bit, and I decided to go with this route. Generally, this type of library should only be used by someone who has read the documentation, and all the instructions should probably be there rather than as actual project output at every build. However, I am planning on making a cargo-muddy CLI tool that will automatically obfuscate a rust project (without the need to import the library). And I think that's where all the output would be important (since it will only run once, rather than every build). Thanks again for the help!
Note for contributor @mrauhu: I know that we spoke about this issue already a couple of times, so I reached out to a few other devs to ask their opinion about how much/if any output text should be produced by the library. There was a pretty strong preference for not having any output at all. I thought about this for a little bit, and I decided to go with this route. Generally, this type of library should only be used by someone who has read the documentation, and all the instructions should probably be there rather than as actual project output at every build. However, I am planning on making a
cargo-muddyCLI tool that will automatically obfuscate a rust project (without the need to import the library). And I think that's where all the output would be important (since it will only run once, rather than every build). Thanks again for the help!