Brandon Blaylock

I've written a few assert law functions for various type classes [here](https://deno.land/x/[email protected]/testing/assert.ts). They are not complete, but I'll likely expand on them as I build that library. If you want...

I spent today expanding my test suite to be more flexible. You can find those tests with fully compliant types in the latest release of hkts [here](https://deno.land/x/hkts/testing/assert.ts). Not that I've...

@raveclassic 1. Queues: throttling an array of requests, two to three at a time, from a list of 20 or more. Not all requests are in pending immediately and the...

> I solved the problem myself. > > v1.8.0 or later with `Deno.emit` support and GitHub Acitons > I installed v1.8.0 or later, which supports `Deno.emit`, and v1.8.2, which is...

This will be done in #4 and wrapped in a nix flake.

I'm partial to semver. Deno is definitely the only target.

I'm not personally interested in supporting Node but I'm also not dead set against it. I figure if you're going to use Node it's more likely that you'll go with...

That sounds great. I'm going to be a bit busy until around Wednesday of next week (2022/03/16) but could probably make time after that from 1000 to 1600 PST on...

Type checking is good enough, I think. Ultimately, test coverage should all be under `./testing` anyway. It's just helpful to know our examples are borked at the type level.

Looks like there is some movement on this in https://github.com/denoland/deno/issues/4716.