It would be beneficial to users if they were able to enable log output when debugging issues with coroutines. One of the main reason this was avoided initially was because we didn’t want to tie users to a particular logging framework. Additionally we didn’t want to introduce any overhead into the library.
Using something like googles flogger would provide performant logging and allow users to include whichever backend matches their current logging framework.
It would be beneficial to users if they were able to enable log output when debugging issues with coroutines. One of the main reason this was avoided initially was because we didn’t want to tie users to a particular logging framework. Additionally we didn’t want to introduce any overhead into the library.
Using something like googles flogger would provide performant logging and allow users to include whichever backend matches their current logging framework.