Tom Dohrmann

I don't see a reason as to why feature gating wouldn't work. I haven't worked on this for a while, but afaict rn proc-macro hasn't changed that much

I think I was refering to watts official demo. I probably just switched proc_macro2 to proc_macro and syn::parse2 to syn::parse and used that

I looked at it again and even though I haven't gotten the demo to work again yet I'm confident that I'll get it running again. For some reason both proc-macro2...

I'm pretty much done now. I've implemented the complete proc-macro Server and even got jit working. I'd welcome some feedback.

@dtolnay I'd appreciate a review

Not sure if this is something, but just wanted to mention the idea: Instead of creating references to `T`, create references to zero sized types. This bypasses the whole `dereferencable`...

Is the only problem with `dereferencable` that it can cause spurious reads? If so, that might not necessarily be a problem for MMIO regions where reads don't have side-effects (e.g....

> > Instead of creating references to `T`, create references to zero sized types. This bypasses the whole `dereferencable` problem by reducing the amount of bytes that LLVM could dereference...

> Ah, but then we would need to store the field offsets somewhere. The offset could be part of the zero sized type for each field e.g. with const generics....

> > Ah, but then we would need to store the field offsets somewhere. > > The offset could be part of the zero sized type for each field e.g....