James M Snell

Ok, before making that change, let me just double check with @nodejs/tsc to make sure nothing has changed that alters the consensus here. If I see nothing by end of...

I think a `searchParams` setter makes the most sense but I also don't see this as a critical issue to address and would likely prefer not to change this. >...

They are different. I have been in the process of extracting Node.js' implementation of key generation into a dependency library that we can pull into workerd to ensure that we...

Changing this to a feature request.

> Let me know if I should update [crypto.ts](https://github.com/cloudflare/workerd/blob/fbd611c858974c63e99bf319e0622e075ce152b4/src/node/crypto.ts#L291) and the doc to mark those as throwing unimplemented. Please do.

`generateKey(...)`, `generateKeySync(...)`, `generateKeyPair(...)`, and `generateKeyPairSync(...)` have all been implemented directly in the runtime now.

The one concern that I have with this is that it is not uncommon for code to destructure assert methods, and if someone destructures them from an `Assert` instance it's...

From the POV of an implementor in Node.js and Cloudflare Workers, I'd definitely be +1 on this and see this as a prereq for adding dispose/async-dispose to various web platform...

> Why not have a single keyword... That works for me also. I'm less concerned with the specific syntax than I am with having *an* ability to declare that an...

Here's an attempt to get something started: https://github.com/whatwg/webidl/pull/1488 It covers only the stand-alone attributes at the moment, e.g. ``` interface Foo { disposer; async_disposer; } ```