std.trace should not hardcode stderr
Open
enhancement
- Dominant language
- Go
- Stars
- 1.8k
- Forks
- 263
- PR merge metrics
- No merged PRs in 30d
Description
When library interface is used we should not assume that `stderr` is the right target for `std.trace` messages. Instead we should provide some API to define where it should go. Probably a Writer interface here in go-jsonnet, but I'm not sure about C api.
Contributor guide
Assessment
This issue has not been assessed yet.