async_kernel VS anuragsoni

A more robust approach would be if every function that needed to log something could look up a unique identifier that's currently active in its context. Blocking applications that use pre-emptive threads can rely on thread-local-storage for this use case and maintain a stack of context ids that can be used by the logging system to determine the current active context id and automatically attach it to a log event. This approach doesn't work for user-mode threaded systems as a single thread can switch between various tasks or systems where a task could potentially jump across threads. Async provides a solution for such context propagation that works at the task level and is naturally called ExecutionContext. Every Async task runs within an execution context, and the context object offers users to append some metadata to its local storage.

All the code in this post can be found here. If you notice any issues let me know via github.

That is all for this post! This took a few tries for me to figure out as a new Kotlin user, and hopefully, some of you will find this useful! If you like this post or have feedback do let me know, either via email or on github.