You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: