Daniel Duque

> ... forcing user to depend on `process-mux` implementation, which might be removed in the future and lacking way to test it. What does this mean? I am a new...

Immediately after this happened, I ran again `rustup update`. Then the output was: ``` [me@lxplus795 ~]$ rustup update info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu' info: checking for self-updates stable-x86_64-unknown-linux-gnu unchanged...

Even though it works, should this be encouraged by the documentation? I don't think that this is the idiomatic way to `print` this error. Using `#from` automatically implements `source`; then...

I tried: ``` llvm-cov show target/x86_64-unknown-linux-gnu/release/fuzz_target_1 --format=html -Xdemangler=rustfilt -instr-profile=coverage/fuzz_target_1/coverage.profdata > index.html ``` And I get: ``` error: Failed to load coverage: 'coverage/fuzz_target_1/coverage.profdata': unsupported instrumentation profile format version ```

What are your current thoughts on this issue? I am currently hesitating against using `nutype` in my projects because I don't want to "pollute" too much the public API of...

For anyone using this same workflow, you can work around it by changing the `{{tag_name}}` replacement for `v{{version}}`. Note that the last `cargo release --execute` will apply your pre-release-replacements again...

This makes sense. Now that I understand how to customize the behavior with individual steps, I don't have a strong opinion about this. On the other hand, there are already...

> What if instead, `nutype` still produced an enum which contains one variant for each step of the validation ? This would "pollute" (even more than it currently does) the...

Maybe good inspiration on how to handle "let users customize errors" can be taken from parser combinator libraries? Feels like `nutype` validation errors can take inspiration on how they handle...

Would this somehow interfere with the `cargo-release` workflow that is already encouraged in the `cargo-dist book`? I would assume that most people using cargo-dist are already using cargo-release as part...