snarkVM icon indicating copy to clipboard operation
snarkVM copied to clipboard

[Proposal] Let dev_println use trace logs

Open vicsn opened this issue 4 months ago • 1 comments

💥 Proposal

Currently, dev_println enabled logs are just printed to stdout (and I assume dev_eprintln to stderr).

We could instead use the trace library, so such logs are easily uniformly retrievable in tmux history and log files.

Is there any downside to doing this?

vicsn avatar Aug 12 '25 13:08 vicsn

I would prefer this too. Having dev_println enabled for test_network in snarkOS creates a lot of output that cannot be hidden.

My guess is the reason for a dedicated dev_println function is so the output shows up in frontend tools that do not use logging frameworks, such as leo.

kaimast avatar Sep 08 '25 17:09 kaimast