jtenner

Also, I wanted to point out that `@parcel/watch` requires the use of `detect-libc`. This wouldn't normally be a problem but... ```ts > await import("detect-libc") Object [Module] { GLIBC: 'glibc', MUSL:...

Hey I appreciate the sarcasm. My work here was a best ditch effort from me as a newbie developer, and I'm sorry for not having enough time to re-contribute back...

As for help with the project, I'm sure this project could always use a pull request.

I would love to even install this via yarn, but the lack of package.json prevents it. I'm thinking about making a pull request with a simple package.json so it's possible...

Second this! I would love to have a shared memory pool between workers.

For my personal use case, it would be nice to allocate a single buffer and have a bunch of workers cooperate together with a lock free allocator. However, I did...

I don't think typescript tooling will like these operators. It will cause people to have to deal with errors in their problems tab. Maybe we can have a `checked(expression)` macro?

Another suggestion might be a `Checked` type.

Right. I was thinking the same thing. How about a grouped postfix `!`. Like this: `(a + b)! `? I think that's valid typescript too.

Using "!" for non null assertions and checked expressions is gonna be confusing too. I'm just at a loss for good options at this point. We are very limited by...