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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: