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

Expose backend identifier information #196

Closed
1 task done
TomAFrench opened this issue Apr 13, 2023 · 0 comments · Fixed by #514
Closed
1 task done

Expose backend identifier information #196

TomAFrench opened this issue Apr 13, 2023 · 0 comments · Fixed by #514
Assignees
Labels
enhancement New feature or request

Comments

@TomAFrench
Copy link
Member

Problem

We currently have no way for nargo to actually know what backend it's interacting with. An example of where this is useful is embedding this into preprocessed artifacts as these are backend specific so it's important to know which backend to use.

Proposed solution

We should add a function which exposes useful information for callers. This could be as simple as exposing the backend identifier but we may want to expose more information such as turbo vs ultraplonk, etc.

Alternatives considered

No response

Additional context

No response

Submission Checklist

  • Once I hit submit, I will assign this issue to the Project Board with the appropriate tags.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
Archived in project
2 participants