Peter Burns
Peter Burns
@Qard I'm not sure which part of my post that's in response to.
Why is that correct? By convention? People can write code with AsyncContext that does require snapshotting and restoring in the constructor (I've seen a real world dependency injection system with...
> This is true of a lot of things. What else are you thinking of here? > I imagine some people will try the pattern outlined in the original post...
The constructor use case came from a project that was aiming to have a tree of providers and consumers, somewhat similar to React context, where any consumer gets its value...
You could work around this by doing, essentially a local implementation of AsyncContext where all of the system's state is stored within a single variable so that it composes. Something...
This is an issue for https://github.com/google/wireit as well
We could, but it'd have to be a breaking change 'cause it changes how marked is packaged, so pretty good chance it'd break users. Counter-question: why use the ancient Polymer...
It's entirely possible that this is an issue in my test harness, this is how I'm calling stream-json: ```typescript const { chain } = require("stream-chain"); const { parser } =...
Agreed on all of those philosophical points. However, I think these three tests are correct in testing the spec as defined by json.org. They check that a string literal with...
If Symbol.dispose was instead a getter on the prototype, or was defined as a function that called this.dispose(), that would alleviate the issue. We'd want to document in that case...