dagenix / libzbase32 Goto Github PK

Our choice of confusing characters to eliminate is: `0', `l', `v', and `2'.  Our 
reasoning is that `0' is potentially mistaken for `o', that `l' is potentially 
mistaken for `1' or `i', that `v' is potentially mistaken for `u' or `r' 
(especially in handwriting) and that `2' is potentially mistaken for `z' 
(especially in handwriting).

0 dkg@hos:…/libzbase32$ cargo --offline test --all-targets --no-default-features 
   Compiling libzbase32 v2.0.1 (…/libzbase32)
error[E0432]: unresolved import `super::decode`
   --> src/decode_impl.rs:264:9
    |
264 |     use super::decode;
    |         ^^^^^^^^^^^^^ no `decode` in `decode_impl`

error[E0432]: unresolved import `super::encode`
   --> src/encode_impl.rs:253:9
    |
253 |     use super::encode;
    |         ^^^^^^^^^^^^^ no `encode` in `encode_impl`

error[E0433]: failed to resolve: use of undeclared type `Vec`
   --> src/decode_impl.rs:268:26
    |
268 |         let mut buffer = Vec::new();
    |                          ^^^ use of undeclared type `Vec`

error[E0433]: failed to resolve: use of undeclared type `String`
   --> src/encode_impl.rs:257:26
    |
257 |         let mut buffer = String::new();
    |                          ^^^^^^ use of undeclared type `String`

Some errors have detailed explanations: E0432, E0433.
For more information about an error, try `rustc --explain E0432`.
error: could not compile `libzbase32` due to 4 previous errors
101 dkg@host:…/libzbase32$