We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export (via nargo export) two functions with the same identifier in different scopes.
nargo export
Two separate JSON documents exported to the export/ directory
export/
The nargo export command brings both into the same scope, does not throw a warning or error, and overwrites one of them.
PoC here
thing.json
src/lib.nr
src/other.nr
Yes
Different names for fn's regardless of scope
Nice-to-have
nargo version = 1.0.0-beta.0 noirc version = 1.0.0-beta.0+f9abf724abd674ea4ccb342a770d237c70864ee1 (git version hash: f9abf72, is dirty: false)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Aim
Export (via
nargo export
) two functions with the same identifier in different scopes.Expected Behavior
Two separate JSON documents exported to the
export/
directoryBug
The
nargo export
command brings both into the same scope, does not throw a warning or error, and overwrites one of them.To Reproduce
PoC here
nargo export
export/
directory to see onething.json
file, rather than the two defined insrc/lib.nr
andsrc/other.nr
Workaround
Yes
Workaround Description
Different names for fn's regardless of scope
Project Impact
Nice-to-have
Nargo Version
nargo version = 1.0.0-beta.0 noirc version = 1.0.0-beta.0+f9abf724abd674ea4ccb342a770d237c70864ee1 (git version hash: f9abf72, is dirty: false)
The text was updated successfully, but these errors were encountered: