Sylwester Rąpała

It's worth to mention that when you run `cargo test` your `dev-dependencies` crates are used in checking your docs example code. But when you build documentation (`cargo +nightly doc`) these...

Can you give me hint how to store a `milivolt` (as a base/store unit)?

My problem is that I want to store `milivolt` `miliamper` etc. and I would need to create own `ISQ!` for each type. I was looking for solution that is similar...

It's look like this will be possible in the future :) [link](https://github.com/rust-lang/rust/issues/44580)

I have also noticed this bug with bool variables.

I don't use this crate anymore. Was the master published in some version and can we close this issue?

Maybe there would be a way to add string error to that? I know that http://nalgebra.org/ has a excellent compile time errors.

Yes, you are right compile time errors are done via trait constanints. Here is an example output. ``` error[E0277]: the trait bound `na::constraint::ShapeConstraint: na::constraint::SameNumberOfRows` is not satisfied --> src/lib.rs:35:40 |...

I think you misunderstood me, I suggest: 1. The cargo-generate requires `{project-name}` to be defined (but not exactly as user input). 2. template is allowed to disable prompt for `{project-name}`...

The level of security will remain the same. The only thing that would change could be the point when `{project-name}` and variables that depend on `{project-name}` will be validated by...