零Rei

Here's the [proposal](https://gist.github.com/mhevery/bb7905da8ef181436a68) as put together for January's TC39 meeting.

As of Node 6, Trevor Norris's [AsyncWrap](https://github.com/nodejs/tracing-wg/tree/master/docs/AsyncWrap) API is a documented, stable part of the core Node API. It would be excellent to port CLS to take advantage of AsyncWrap...

@askhogan This sounds like a question for @hayes -- It could be as simple as making sure that `newrelic` is required before `continuation-local-storage` in your application, or there could be...

@vdeturckheim I'd have to investigate the `newrelic` and AppDynamics agents to be sure, but I believe that the fact that this works with one order and not the other means...

Needs a test and to pass the eslint checks, but aside from that this looks useful. Thanks for your time!

I'll need to do some investigation to figure out if this is a problem with CLS or the underlying asyncListener API, but until I have a chance to do that,...

Can you describe what you mean by "chaos"? It looks like you're using generators and Promises to do sugarless async / await, which should work fine with CLS as long...

> In the very first code example in your README.md, you have `session.set('user', user);` which doesn't seem to be enclosed in a `session.run()`. The first 2 examples are probably a...

Thanks, Tim! Do you need this just for Redis? I'm considering maybe folding these shims into `cls-redis` and applying them automatically (and maybe eventually pulling that up into CLS itself)....

Probably by patching the module loader, and you're right about it being intrusive. However, short of turning CLS into a source-to-source transformer like browserify or streamline, it's the only way...