Yes, I think that I'm being unclear. As a user, I need to understand the top level abstraction of the library I am using - the api. I need to read that api's c

Yes, I think that I'm being unclear. As a user, I need to understand the top level abstraction of the library I am using - the api. I need to read that api's code and understand what it does, (not any deeper) in order to use it. If it is a low-level api that directly implements a thread-pool, I need to understand that. If it is a high-level template that implements the async continuation monad[1], I need to understand the api surface that I call, and just the body of that surface and type signature. 1: https://www.fpcomplete.com/blog/2012/06/asynchronous-api-in-c-and-the-continuation-monad https://www.fpcomplete.com/blog/2012/06/asynchronous-api-in-...