Ron Buckton

This should be fixed in `[email protected]` and it now should be able to load side-by-side with `[email protected]`

I've been planning on an overhaul of the library for some time to include support for functional style operations as well as queries over `AsyncIterable`, in addition to a documentation...

This has been published to npm as `1.0.0-pre.0` and is available now. There are a number of breaking changes in directory structure (i.e. "out" was renamed to "dist") if you...

Also as an fyi, I just published a related project: https://www.npmjs.com/package/iterable-query-linq. It allows you to use a LINQ-like FLWOR syntax using tagged template expressions: ```ts import { linq } from...

> AFAIK other than this, declarations aren't conditionally evaluated inside a scope. This weirdness means that you have to check at runtime whether a binding actually has a disposable resource....

> Having `using` declarations in bare switch cases just seems always like a mistake: the programmer most likely mistakenly thought that each case has its own block scope. I'd prefer...

I am aware, and mentioned that during the meeting as well.

@bmeck I made [your comment](https://github.com/tc39-transfer/proposal-csprng/pull/2#issuecomment-582939183) into an [issue](https://github.com/tc39-transfer/proposal-csprng/issues/3) so that we can ensure we track this and follow up with someone from Node about concerns and possible remediations.

I don't believe this to be a web compatibility issue, however. *Not* throwing an error shouldn't make any existing code break today, though it would be worthwhile to discuss this...

@bakkot I've also made your comment above a separate [issue](https://github.com/tc39-transfer/proposal-csprng/issues/4) so that we can track the discussion.