Skip to content
This repository was archived by the owner on Mar 13, 2026. It is now read-only.
This repository was archived by the owner on Mar 13, 2026. It is now read-only.

Unify conventions around usage of big.Int #294

@fmoletta

Description

@fmoletta

Some functions use big.Int as arguments, while others use *big.Int. The same happens with scope variables, some hints store them as references while others store their value, which can lead to bugs in cross-hint interaction. We should have a unified criteria to avoid any kind of confusions.
I suggest sticking to *big.Int, as this is what all functions and methods in the big package use

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions