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
I was wondering if we could have some sort of thread local logger (possibly adaptors for coroutine local as well), this way you wouldn't have to pass the logger around in most cases, making the crate much more ergonomic.
It wouldn't work for all occasions, granted, but I can see it being very useful in a lot of cases.
The text was updated successfully, but these errors were encountered:
So loggers can be used as immutable, are Sync+Send, so I believe they could be put into a global, and have a closure that prints some values from thread-local variables.
One could also store them in thread-local itself, pass to a spawned thread and save there, I believe.
I haven't really though about it yet and I'm open for feedback and ideas.
I was wondering if we could have some sort of thread local logger (possibly adaptors for coroutine local as well), this way you wouldn't have to pass the logger around in most cases, making the crate much more ergonomic.
It wouldn't work for all occasions, granted, but I can see it being very useful in a lot of cases.
The text was updated successfully, but these errors were encountered: