Closed Serpent03 closed 1 week ago
No, dont use println, shift to a proper logging package, m open to using any crate like tracing, slog or log
No, dont use println, shift to a proper logging package, m open to using any crate like tracing, slog or log
Then tracing is probably a better approach to logging(atleast intermediately) since it supports concurrent operation logging
Should we open another issue and then submit a PR in relation to that for enabling logging globally?
No, dont use println, shift to a proper logging package, m open to using any crate like tracing, slog or log
Then tracing is probably a better approach to logging(atleast intermediately) since it supports concurrent operation logging
Should we open another issue and then submit a PR in relation to that for enabling logging globally?
sounds good to me
just open an issue and i'll just link it here for reference, after that i'll merge
Merged and deleted after opening issue #18
Add in error handling and
println!()
logs for clarity(for the time being).Fix hangups from empty TCP pipes(not tested fully).