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
NoirJS will currently throw an error whenever it encounters a foreign call opcode within a brillig block. This is because the default foreign call handler doesn't know how to process any of these.
This is problematic as std::println is a common function which may exist in a circuit if a user is debugging using JS. It would be nicer if we had a handler for this foreign call type so that JS users can print values from their circuits without needing to write it themselves.
Happy Case
We should write a function in JS to properly format std::println calls and console.log them.
Problem
NoirJS will currently throw an error whenever it encounters a foreign call opcode within a brillig block. This is because the default foreign call handler doesn't know how to process any of these.
This is problematic as
std::println
is a common function which may exist in a circuit if a user is debugging using JS. It would be nicer if we had a handler for this foreign call type so that JS users can print values from their circuits without needing to write it themselves.Happy Case
We should write a function in JS to properly format
std::println
calls andconsole.log
them.Alternatives Considered
No response
Additional Context
#3294 (comment)
Would you like to submit a PR for this Issue?
No
Support Needs
No response
The text was updated successfully, but these errors were encountered: