Kitlith

There are also ways to make it work by using auto(de)ref. Take this example: ```rust #[binrw] struct Test { #[brw(assert(field.ne(&0u8)))] field: u8, } ``` by writing the condition as `field.ne(&0u8)`...

Unsure. For operators we might be able to get something to work by parsing and replacing uses of operators with uses of traits. This strikes me as error-prone, though. I'd...

Correct me if I'm wrong, but if you go through the kernel by using uinput then you wouldn't need to worry about X11/Wayland/etc...? EDIT: there's a library for this: https://github.com/meh/rust-uinput...

I've been poking at the bit_order branch recently, it basically seems down to assumptions that Msb bit order is being used. On the write side, I was able to produce...

As a side note, we could probably use the methods on the BitField trait from bitvec to simplify the implementation. I'm assuming there's some reason why it doesn't seem to...

Is there anything preventing us from, say, doing something similar to what steam's proton does to handle steam client stuff under wine?

Well, I figured we could use proton's thing to perform dll so, and then use your current stuff in place of the official one(s)? I dunno.

could possibly side-step the ordinary restrictions of JIT by compiling a bunch of gadgets at compile time and jumping between them, the output of the JIT would be a list...

> The JIT mentioned is the guest JIT we use to translate game code to host code. Obviously we can't do any sort of code generation for that at compile...

yeah, I run into similar issues too, but not necessarilly limited to starting with gdb.