Skip to content
New issue

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

Exported Functions Share Namespace #6772

Open
jtriley-eth opened this issue Dec 11, 2024 · 0 comments
Open

Exported Functions Share Namespace #6772

jtriley-eth opened this issue Dec 11, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@jtriley-eth
Copy link
Contributor

jtriley-eth commented Dec 11, 2024

Aim

Export (via nargo export) two functions with the same identifier in different scopes.

Expected Behavior

Two separate JSON documents exported to the export/ directory

Bug

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

  1. clone repo and enter the directory
  2. nargo export
  3. check export/ directory to see one thing.json file, rather than the two defined in src/lib.nr and src/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)

@jtriley-eth jtriley-eth added the bug Something isn't working label Dec 11, 2024
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Noir Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant