Jacob Lifshay

support for WASM, for improved performance (SIMD, ability to opt-out of dynamic types and GC, multithreading with shared memory, more integer and floating-point types, direct access to memory) and ability...

> True, forgot to check that. I think I'd prefer making `pat` fragments match only `PatternNoTopGuard` to gating it on a new edition, since you can always just wrap the...

> ```rust > (A(x, y) if x == y) | B(x) => ... > ``` `x` is bound in both branches, maybe you meant `y` since that's not mentioned in...

> I have no objection to requiring AVX2. Especially as it has been around since 2013, which is longer than the version of opengl we require. I'll mention that Intel...

> Is it possible to have HDR require AVX2 while having completely SDR workflows not require it? I think it is safe to assume that anyone doing HDR is likely...

> Feel free to give an argument for why it shouldn't here's a try: it could be less efficient because to send it to the decklink card, it'd likely have...

I expect some uses of `Mutex` and similar to not count as blocking, e.g. the following should not count imho: ```rust pub struct AtomicId(Mutex); impl AtomicId { pub const fn...

one place where blocking should be allowed is in things like genawaiter, which is a library for making generators built on top of the async/await mechanism, where it's like having...

> And given that `genawaiter` is used like `gen!({ ... })` the expanded macro could easily be `#[allow(blocking)] async { ... }`. I'm saying there should be an attribute like...

one other problem with just having macro matchers for each ast thing and then writing out rust's syntax explicitly in the macro pattern is that iirc macro_rules isn't powerful enough...