Alexander van Saase

I'm not flying INAV anymore, or much at all. There were also some conflicts that would need to be resolved. If someone wants to pick this up again they are...

It would be nice if the user can supply the grid cells that they want to mask. That way the user can determine from themselves what they consider sensitive and...

Marking things `Send` that are fundamentally not `Send` feels wrong but I still think it's the best way forward. If I understand correctly, the main issue is that JS types...

There are more places where axum requires `Send`/`Sync`, most notably the state that you attach to the router.

> I'm just a little worried about having to go through wrap every single type. It feels time consuming and error prone. This addresses the issue right at the handler...

Hmm, I see how creating `Send` and `Sync` wrappers for the JS types can become quite complex. For advanced use cases like ours I think it's not too uncommon to...

I tried to get the example in the OP working by implementing `Send`/`Sync` for all the R2 types (https://github.com/cloudflare/workers-rs/commit/63cb306e50f94c6664955ba40c7940091fae56e8) but it still complains about `Rc` not being thread safe. It...

Maybe the macro is the best solution after all. We'll have to `unsafe` implement `Send` and `Sync` for our app state (which I was hoping to avoid) but I think...

After thinking about this some more this I think there are two ways to go about this that will yield a good developer experience: 1. Push the `unsafe impl Send/Sync`'s...

Here's the example I created when I was trying to debug a trait bound error on a middleware: ```rust use axum::{ body::Body, extract::{Request, State}, http::HeaderMap, middleware::{from_fn_with_state, Next}, response::Response, routing::get, };...