Daniel Svensson

Updated with Spike's take on this change. Changed temporarily to Draft PR, need to read through a final time.

Verified in wasm, linux statically linked, linux dynamically linked.

fixed in the pending megadiff from spike

``` @SomeAnnotationCompatOrSupportOrSomething(R.id.frag_something) SomeFragment foo ``` Instead of what I wrote above

Here it's the other way around :)

This probably requires some broader macro that replaces the per-register-type enum with macro expansion as there's not really a good link between the register value wrappers and the register address...

I'm adding some wiggleroom in #21 to simplify experimenting with other ways of functioning.

@chocol4te As I see it, a low level module, or different crate will do what the constructor does today, and be responsible for, via public APIs, interacting with the registers....

@chocol4te I'll be offline for the next 10 days or so, but I've pushed #21 which prepares the exposing thing, and created #22 for the second part of that. Ideally...

@chocol4te I've done said change now. Next up will be to change the macros to get proper type safety around the write/read methods. So now you chose between the limited...