Skip to content
This repository has been archived by the owner on Oct 11, 2024. It is now read-only.

Investigate possible truncation #678

Open
recmo opened this issue Apr 29, 2020 · 0 comments
Open

Investigate possible truncation #678

recmo opened this issue Apr 29, 2020 · 0 comments
Assignees
Labels
refactor Improves the code quality tracker Issues generated from source comments

Comments

@recmo
Copy link
Contributor

recmo commented Apr 29, 2020

On 2020-04-29 @pvienhage wrote in 7850bac “Smart contrat Recurance proof system impl (#677)”:

Investigate possible truncation

    about = "Example zkp-stark project verifying Pedersen Merkle trees."
)]
struct Options {
    // The number of occurrences of the `v/verbose` flag
    /// Verbose mode (-v, -vv, -vvv, etc.)
    // TODO - Investigate possible truncation
    #[allow(clippy::cast_possible_truncation)]
    #[structopt(short, long, parse(from_occurrences))]
    verbose: u8,

    /// Run a specific 8192 depth example

From crypto/stark/examples/pedersen_merkle/main.rs:73

@recmo recmo added refactor Improves the code quality tracker Issues generated from source comments labels Apr 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
refactor Improves the code quality tracker Issues generated from source comments
Projects
None yet
Development

No branches or pull requests

2 participants